[haiku-commits] Re: BRANCH midar-github.master - src/system/libroot/posix/glibc/stdio-common src/servers/app src/kits/app src/apps/icon-o-matic/shape headers/os/support
- From: Jonathan Schleifer <js-haiku-commits@xxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sun, 25 Nov 2012 20:05:35 +0100
Am 25.11.2012 um 15:39 schrieb Ingo Weinhold:
> I'm not aware of any incompatibilities. Care to elaborate?
C is not a subset of C++, they are, in fact, two different languages. The list
of differences is quite long, actually. See
http://en.wikipedia.org/wiki/Compatibility_of_C_and_C%2B%2B
> We don't have a static libroot and since ATM there are no plans for a binary
> compatible kernel interface, there probably won't be any anytime soon (at
> least it wouldn't make much sense).
So we should just never allow static binaries then, just to fix a glibc issue
that can be fixed without adding a C++ dependency?
> You'll be horrified to learn that our libroot already uses C++. The gcc 4
> version is statically linked against libsupc++. Both gcc 2 and gcc 4 have
> also compiled in libgcc. For gcc 2 we can't really change that. For gcc 4 we
> should eventually disentangle things (i.e. link against the shared libgcc and
> libsup++ instead).
Yes, that sounds sane. After all, there is not much sense in linking libsup++
for a pure C program.
>> That whole file is ugly (like the rest of this ancient glibc), so I don't
>> see why we should really bother? We should instead focus on importing a
>> newer and more sane libc for gcc4.
>
> +1
What happened to the patch to add a BSD-based libc, btw?
--
Jonathan
Other related posts:
