Michael Schmitt <[EMAIL PROTECTED]> writes:
| Once again the question raises whether this is a Sun CC specific feature
| or whether this is a behaviour clearly stated in the ANSI standard. I
| guess that Sun CC is right.
Sun CC is not right, but the above is often used as an iterim solution
when waiting for clearification on how to really follow the standard.
The standard says that all ANSI C function shall be in std this
excludes macros.
| What does this mean for Lyx? First all, everything is fine. (Sun
| expected you to write code in that manner) However, if you want to make
| Lyx a modern C++ program you should change any old-fashioned include
| statement into the more modern counterpart. (Do a global search and
| replace, check in the code and I will try to compile it)
Where have you found old-fashioned included statemens now?
| In the special case of "abort" both alternative include statements were
| used in the same file (or more precisely in their header files' header
| files). Hence, the name space problem did not occur.
|
| Have a good night (hope you sleep tight despite the problem which is
| none in principle :-)
|
| Michael
|
| PS: Once again, I would like to point out that csignal does not include
| "kill", even though signal.h does. "kill" does not seem to be a ANSI C++
| standard function.
it is "UNIX" or/and and os/system function and has noting (except its
interface) to do with ANSI C or ANSI C++.
Lgb
