Re: "14 % 8" for example...

From: James Giles (jamesgiles_at_worldnet.att.net)
Date: 10/01/04

  • Next message: Robert Corbett: "Re: operator overloads and the Sun Fortran compiler 6.2"
    Date: Fri, 01 Oct 2004 00:32:09 GMT
    
    

    bv wrote:
    > glen herrmannsfeldt wrote:
    >>
    >> I was guessing that it would be ambiguous with certain operators
    >> that are dot delimited.
    >>
    >> X=A.GE.B
    >
    > Considering the ways how ADA could parse such an expression it would
    > seem incredulous that an old timer like Fortran could stumble on its own
    > *keyword*.

    First, it's not a keyword, it's an intrinsic operator.

    Second, even if it was a keyword, keywords are not reserved
    in Fortran.

    Both intrinsic operators and keywords must be use in ways consistent
    with the rules of Fortran or they're likely to be ambiguous or just
    wrong. The rules of Fortran don't permit the above to be interpreted
    as a subobject name. Implementations the permit such extensions
    should do so carefully and not misinterpret the above. I wouldn't
    use the extension anyway. Nor would I recommend that anyone
    else do so.

    -- 
    J. Giles
    "I conclude that there are two ways of constructing a software
    design: One way is to make it so simple that there are obviously
    no deficiencies and the other way is to make it so complicated
    that there are no obvious deficiencies."   --  C. A. R. Hoare
    

  • Next message: Robert Corbett: "Re: operator overloads and the Sun Fortran compiler 6.2"

    Relevant Pages

    • Re: fortran 200X proposal: "use none" counterpart to "implicit none"
      ... having lots of special cases placing high burden on Fortran ... On the USE statement you can specify the module nature ... to have a "NONE" keyword seems like a better idea. ...
      (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)
    • RE: Integrated Developement Environment - looked for...
      ... There are a number of F90 extensions already in the Open Watcom F77 compiler: ... FORTRAN 90 Compliant Extensions ... The following additional I/O specifiers for the INQUIRE statement are supported: ...
      (comp.lang.fortran)

    Loading