This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi! Several things break because glibc 2.2 declares exit with throw() while it did not do that previously. The issue is that if you include stdlib.h (even indirectly) and declare yourself void exit(int); C++ errors on it. I'm not sure if the right way is to fix all those crapy programs or if it would not be easier to just kill the __THROW on exit. It is declared noreturn, so in my understanding a noreturn function should not throw exceptions either, because then it would actually return, I haven't seen any differences in g++ output but there of course could be some... One thing which would be hard to fix is autoconf, which declares exit itself (of course without throw(), so when some configure.in sets current language to c++ and a test includes stdlib.h, it will die). Ideas? Jakub
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |