fails to compile the valid code

[Uttam Pawar]

On Tue, 2005-11-22 at 21:00 -0500, Erik Zeek wrote:
> On 11/22/05, Uttam Pawar <uttamp@us.ibm.com> wrote:
> >
> >
> > xlf95 has std flag which is set by default.
> >
> > - Uttam
> >
> 
> This is off by default on my xlf95 (8.1, Mac OS X) version:
> 
>        -qlanglvl=<suboption>
>               Determines which language standard (or superset or subset of a
>               standard) to check against for nonconformance.  Suboptions
>               include:
> 
>               77std
>                    Accepts the language specified by the ANSI Fortran 77
>                    standard.
>               90std
>                    Accepts the language specified by the ISO Fortran 90
>                    standard.
>               90pure
>                    Same as 90std, except that it reports errors for any
>                    obsolescent Fortran 90 features used.
>               95std
>                    Accepts the language specified by the ISO Fortran 95
>                    standard.
>               95pure
>                    Same as 95std, except that it also reports errors for any
>                    obsolescent Fortran 95 features used.
>               extended
>                    Accepts the full Fortran 95 language standard plus all
>                    extensions, effectively turning off language-level
>                    checking.  This is the default.
> 
I've xlf95 (version 9.1 on PowerPC)
I could use -qlanglvl=95std (or 95pure), option, xlf95 still compiles
the code, with a warning, 
"1518-240 (L) The name mytype was already encountered as the name of
another entity in this scope.  This is not permitted by the Fortran 95
standard, except that the name of a generic procedure may be the same as
the name of one of its specific procedures".


- Uttam