Where's std.h?

Where's std.h?

[neal]

I'm trying to build ptolemy-0.7 using egcs-971105 glibc2.0.5.  There
is no <std.h>.  Is this standard or not?

Re: Where's std.h?

[Joe Buck]

> I'm trying to build ptolemy-0.7 using egcs-971105 glibc2.0.5.  There
> is no <std.h>.  Is this standard or not?

No, std.h is not standard, it is a libg++'ism.  (I was responsible for
putting that into Ptolemy years ago, but you probably want to replace
uses of std.h with the appropriate standard headers, such as <stdlib.h>
and <string.h>).

Re: Where's std.h?

[Neal Becker]

>>>>> "Joe" == Joe Buck <jbuck@synopsys.com> writes:

    >> I'm trying to build ptolemy-0.7 using egcs-971105 glibc2.0.5.  There
    >> is no <std.h>.  Is this standard or not?

    Joe> No, std.h is not standard, it is a libg++'ism.  (I was responsible for
    Joe> putting that into Ptolemy years ago, but you probably want to replace
    Joe> uses of std.h with the appropriate standard headers, such as <stdlib.h>
    Joe> and <string.h>).


Thanks.  I just wish I could find something to test to determine what
is the libstdc++ version so I could make the changes conditional.
Any ideas?

Re: Where's std.h?

[Joe Buck]

Joe> No, std.h is not standard, it is a libg++'ism.  (I was responsible for
Joe> putting that into Ptolemy years ago, but you probably want to replace
Joe> uses of std.h with the appropriate standard headers, such as <stdlib.h>
Joe> and <string.h>).
> 
> 
> Thanks.  I just wish I could find something to test to determine what
> is the libstdc++ version so I could make the changes conditional.
> Any ideas?

In principle, you can make the changes unconditional.  All std.h does
is include other headers; just include the ones you need instead.  This
will not break the code when you use older g++ ports.  As I said, it
should have been done that way originally.