> >From section 10.6 of the DIGITAL Fortran Language Reference Manual,
> April 1997, which used to be distributed with Digital Visual Fortran:
>
> "TYPE is a synonym for PRINT. All forms and rules for the PRINT
> statement also apply to the TYPE statement."
>
> TYPE is not a keyword in standard Fortran (and the manual acknowledges
> this by printing the information about it in a blue font).
To correct my error, of course TYPE is a keyword used to declare
derived types, but its use as a synonym for PRINT is nonstandard.
Re: TYPE *, SYSTEM executable statement ... > I am developing some data processing code on a Compaq SC45.... > gives me a floating point exception and the program dies (just after ... >>From section 10.6 of the DIGITAL Fortran Language Reference Manual,... which used to be distributed with Digital Visual Fortran:... (comp.lang.fortran)
Re: "14 % 8" for example... ... > seem incredulous that an old timer like Fortran could stumble on its own ... First, it's not a keyword, it's an intrinsic operator. ... Implementations the permit such extensions... no deficiencies and the other way is to make it so complicated ... (comp.lang.fortran)
Re: Hows dot.net doing nowadays? ... By the time MSC came along "PASCAL" became the more common keyword.... [I should probably add, before someone nails me, fortran and stdcall are ... the VAX compilers all were essentially language-neutral for ... all languages which was a wonderful feature of VMS... ... (microsoft.public.vb.general.discussion)
Re: void pointer ... interfere with it use as an identifier if the designer makes the right ... I had missed that you were assuming a particular syntax.... that is in the implementation name-space (i.e. _Fortran).... but also acts like a keyword in the right context. ... (comp.lang.c)
Re: Hows dot.net doing nowadays? ... Another common keyword in the early days was _basic. ... [I should probably add, before someone nails me, fortran and stdcall are not ... the VAX compilers all were essentially language-neutral for all languages which was a wonderful feature of VMS... ... (microsoft.public.vb.general.discussion)
