Remember I posted that message showing that Watcom was polluting
the namespace by using "_cstart" as a function name? Well I now
know the reason for using a name, it is to link in the startup
code "automatically". Thanks to PDPCLIB, I was able to check
what I did for the other compilers, and GNU uses __main, which is
fine, Borland doesn't seem to use any, so you have to manually
link in the startup code, and CSET is buggy too, using _exeentry...
/* This program demonstrates a problem with CSET++/2 2.0.
It is polluting the namespace with "_exeentry", so that
when you try and link you get problems. There is nothing
wrong with me calling a function _exeentry. They should
have instead called theirs either __exeentry or _Exeentry,
according to ISO/IEC 9899:1990. Paul Edwards, 3:711/934{at}fidonet */
#include
void _exeentry(void)
{
printf("hi\n");
return;
}
int main(void)
{
_exeentry();
return (0);
}
@EOT:
---
* Origin: X (3:711/934.9)
|