Jan-Jaap van der Geer wrote:
Peter Naulls <[EMAIL PROTECTED]> wrote:
Strictly speaking, libstdc++ makes use of malloc for 'new'. This
is almost always true in C++, except in some very unusual setups
- GCC itself doesn't know much about it except for syntax
reasons. libstdc++ might also use malloc internally, although I
suspect not. UnixLib also uses malloc internally for various
uses - mostly for some initialisation purposes, but also for some
filename conversion stuff.
Thanks.
Talking about libstdc++, I assume using the standard C++ classes
(string, iostream, stl) means the resulting executable becomes
dependent on SharedUnixLib? Looking at the info on riscos.info I
could not find anything to suggest that this is the case.
I did find references that it was possible to compile/link with
-mlibscl, but apparently that did not mean that UnixLib is *not*
used.
Not quite. Use of _UnixLib_ requires the SharedUnixLib module.
Whether or not you use UnixLib with C++ is another matter, but
that is the default - i.e, opposite use of using -mlibscl.
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
