Re: Accept Date YYYYMMDD
Date: 30 Nov 2003 10:10:30 -0800
"James J. Gavan" <jjgavan@shaw.ca> wrote
> "The YYYYMMDD phrase on the ACCEPT statement was not part of the 1985
> standard. It was first standardized in the 2002 ISO standard. However,
>
> long before that, J4 agreed to "freeze" this new feature that was
> developed
> for the 2002 so that compiler writer's could implement it before the
> year
> 2000 and users could make use of this feature, knowing that it would be
> portable among implementations. ".
But how many compiler writers did actually implement it ? MF did,
though it is not documented in OCDS 4.1. Fujitsu did not even in 7.
Relevant Pages
- Re: Is C99 the final C? (some suggestions)
... > that someone will try compile their stuff on an old compiler. ... > because the ANSI standard obsoleted them, and everyone picked up the ANSI ... fixed by using another language. ... >>are multiplying two expressions of the widest type supported by your ...
(comp.lang.c) - Re: Statement on Schildt submitted to wikipedia today
... to working programmers and more with being "right all the time, ... so that compiler developers could be shed ... The major corporate interests were compiler developers, ... processors, committed to standard division semantics, and otherwise ...
(comp.lang.c.moderated) - Re: __VA_ARGS__ and the DDK compiler
... his questions are related more to the difference between MS and the ISO standard. ... If his questions concerned a Visual Studio product then microsoft.public.vc.language would be the place for them, but it looked to me like he might be using a compiler that came in a DDK. ...
(microsoft.public.development.device.drivers) - Re: #define and (brackets)
... Minor compiler vendors are free to join if they are so inclined, ... analysis hasn't changed between the two versions of the standard. ... This bug is a minor bug in an obscure ...
(microsoft.public.vc.language) - Re: interesting use of NEXT SENTENCE vs. CONTINUE
... Program name in quotes (allowed in '02 Standard) ... > If J can be made an independent item which the compiler can put wherever it ... > has to be associated with a hardware device in SPECIAL-NAMES. ... > that ALTER *always* modifies the address parameter of the hardware branch ...
(comp.lang.cobol) |
|
