This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
[I'll be amazed if his address doesn't bounce back!]
>A colleague talks me about egcs for testing Y2K compliance at compilation
>time.
>Thus, I have downloaded egcs1.1.1 (2.93.06 of 1999-02-08) and compiled my
>application with it in order to verify this feature.
>Unfortunately, I have obtained none result (warnings for example) in this
>sense.
>I have not found any discussion or FAQ about this feature on your site
>either.
>
>So, my question is :
> Has egcs Y2K verification features ?
>
>Thank you for your answer to this topical question.
I don't believe egcs has any Y2K verification features. We expect
to have them in the next major release of egcs, version 2, due out
in February, 1901. :)
More seriously, perhaps some egcs front ends could issue warnings
for uses of library functions known to have non-Y2K-compliant
interfaces. In fact, just last week, I was getting some positive
responses from some long-time g77 alpha testers to the proposal
that we have g77 do this, e.g. warn about a reference to the IDATE
intrinsic. We might do this for egcs 1.2.
Take a look at <http://www.gnu.org/software/year2000-list.html>,
for some information on Y2K readiness of GNU products, though I
can't recall whether egcs is specifically listed. (Make sure
you check <http://www.cygnus.com/egcs> for that, though I haven't
myself, recently. Can't see any pertinent references to "Y2K"
or "2000" in my local copy of the html docs.)
tq vm, (burley)