Very Computer

How do we obtain this warning in Alpha FORTRAN?

--

Quote:> In VAX FORTRAN the complier warns if a variable has been declared but not used.

> How do we obtain this warning in Alpha FORTRAN?

        $ FORTRAN /WARN=DECLARATION

or

        IMPLICIT NONE

Last time I checked, warnings for undeclared variables were not the
default on VAX Fortran.

Tim, who does remember using this feature but its so long since he used Fortran someone
else will have to answer.
--
Tim Llewellyn, OpenVMS System Manager, Remarcs Project
MedAS at the BBC, Whiteladies Road, Bristol, UK.

I speak for myself only and my views in no way represent those of
MedAS or the BBC.

IMHO one of the it's-a-feature-not-a-bug of Fortran is that you do
not have to give a type for every variable; just use it.   OK, after a
few edittings there may be a few stray names around; if that
stray name were a variable with a dimension of (999999999), that could
cause a problem to some operating systems, and is a valid reason
for always checking those names and removing them from the coding.
But I claim that the misspelling case is more important.

If neither of these cases apply (i.e. if you can withstand some
imperfect code, in the interest of getting some real answers, quickly)
then you do not even need to know these names.   Your time
and thought are part of the "expense" too.

--
Brendan Welch, system analyst, Univ. of Massachusetts - Lowell, W1LPG

"Hans M. Aus" a crit :

Quote:

> In VAX FORTRAN the complier warns if a variable has been declared but not used.

> How do we obtain this warning in Alpha FORTRAN?

$  fortran /warning=unused program.for

Sincerly.

___  Pascal Blonde _________________________ ICQ: 24454327 ________

Fax: (33/0)1 4325 5542  http://opdaf1.obspm.fr/~pascal/pblonde.html
---------______ LPTF, Observatoire de Paris, France _____----------

He wants to find declared but unused variables not used but undeclared
variables.

Arne

FORTRAN/WARNINGS=DECLARATIONS only picks the variables
used but not declared. Not what was requested. I used to refuse to debug
student fortrash unless it had IMPLICIT NONE or was compiled
/WARNINGS=DECLARATIONS, btw.

Fortran/warnings=unused flags unued variables, as requested by Hans
M. Aus.

This is Digital Fortran V 7.1.

Regards

--
Tim Llewellyn, OpenVMS System Manager, Remarcs Project
MedAS at the BBC, Whiteladies Road, Bristol, UK.

I speak for myself only and my views in no way represent those of
MedAS or the BBC.

Quote:> In VAX FORTRAN the complier warns if a variable has been declared but not used.

> How do we obtain this warning in Alpha FORTRAN?

        /WARN=UNUSED

The $help  F90/Warn lists only:

  /WARNINGS=(option[,...])    D=/WAR=(ALI,NODEC,GEN,UNCALL,UNINIT)

/Warnings=ALL is the default.

No warning message appears when I compile a file with a declared but
unused variable using:

$for/warn=unused test

Also, the compiler accepts the keyword "/warn=unused" without an error.

Whereas,

$f90/warn=blabla test.for
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
 \BLABLA\

:-|

--

Quote:>In VAX FORTRAN the complier warns if a variable has been declared but not used.

>How do we obtain this warning in Alpha FORTRAN?

be nice to know how many Fortran users agree with what I would like -- mostly
the old VAX behaviour.

Regards, Paddy

Paddy O'Brien,
System Planning,
TransGrid,
PO Box A1000, Sydney South,
NSW 2000, Australia

Tel:   +61 2 9284-3063
Fax:   +61 2 9284-3050

Either "\'" or "\s" (to escape the apostrophe) seems to work for most people,
but that little whizz-bang apostrophe gives me little spam.

I have asked the Fortran engineering team to make this the default for /old_f77
and F90/F95, as was on VAX.  Since they will not, I assume that there are
powerful people out there who have requested otherwise.

Unless you have specific F90/F95 code, try compiling on a VAX platform to get
better warnings/informationals.  

I hope that eventually the team will give us the warnings we had in their VAX
compiler.

Regards, Paddy

Paddy O'Brien,
System Planning,
TransGrid,
PO Box A1000, Sydney South,
NSW 2000, Australia

Tel:   +61 2 9284-3063
Fax:   +61 2 9284-3050

Either "\'" or "\s" (to escape the apostrophe) seems to work for most people,
but that little whizz-bang apostrophe gives me little spam.

Quote:>We're using  Digital Fortran 90 V7.1-330 on our Alpha.

>The $help  F90/Warn lists only:

>  /WARNINGS=(option[,...])    D=/WAR=(ALI,NODEC,GEN,UNCALL,UNINIT)

>/Warnings=ALL is the default.

>No warning message appears when I compile a file with a declared but
>unused variable using:

>$for/warn=unused test

>Also, the compiler accepts the keyword "/warn=unused" without an error.

>Whereas,

>$f90/warn=blabla test.for
>%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
> \BLABLA\

On the June Condist, Fortran has been upgraded to F90/F95.  It also includes
some (but not all) of the things we were used to and loved on the old VAX and
early Alpha F77.

Regarding qualifiers and keywords, I believe that though they are not effective,
all the original keywords are left in place for compatibility.

As a long time user of VAX Fortran and the facilities (qualifiers, etc.) we were
given, I would love to know what VMS Alpha F90/F95 users feel that they are not
getting that we were used to.  Or even what has changed; -I- becomes -W-, etc.
(screws MMS).

I am preparing my own "hit-list" that I intend to send to the Fortran team, and
would love to share with dedicated (Digital - VMS) Fortran users.  Write
privately or to the newsgroup.

Regards, Paddy

Paddy O'Brien,
System Planning,
TransGrid,
PO Box A1000, Sydney South,
NSW 2000, Australia

Tel:   +61 2 9284-3063
Fax:   +61 2 9284-3050

Either "\'" or "\s" (to escape the apostrophe) seems to work for most people,
but that little whizz-bang apostrophe gives me little spam.

Quote:>On Alpha, /warn=unused.
>I have asked the Fortran engineering team to make this the default for
> /old_f77
>and F90/F95, as was on VAX.  Since they will not, I assume that there are
>powerful people out there who have requested otherwise.
>Unless you have specific F90/F95 code, try compiling on a VAX platform to get
>better warnings/informationals.  

              1         integer a,b,c
                ..................1.2
%FORT-I-VARUNUSED, (1) Variable was declared but not used.

%FORT-I-VARUNUSED, (2) Variable was declared but not used.

              2         real mean
              3
              4         a=3
              5         mean=a
              6         write(*,*)mean
              7         stop
              8         end
[snip]
/WARNINGS=(ALIGNMENTS,ARGUMENT_CHECKING,DECLARATIONS,GENERAL,INFORMATIONAL,
TRUNCATED_SOURCE,UNCALLED,UNINITIALIZED,UNREACHABLE,UNUSED,USAGE)
================
but f90/warn gives:
===============
FOO$MAIN$BLK                    Source Listing                  
14-JUL-1999 14:02:22  DIGITAL Fortran 90 X7.1-574       Page 1
14-JUL-1999 14:01:15  USR_SCROOT:[REID]FOO.FOR;1

              1         integer a,b,c
              2         real mean
              3
              4         a=3
              5         mean=a
              6         write(*,*)mean
              7         stop
              8         end
[snip]
/WARNINGS=(ALIGNMENT,ARGUMENT_CHECKING,DECLARATIONS,GENERAL,GRANULARITY,
TRUNCATED_SOURCE,UNCALLED,UNINITIALIZED,USAGE)

--

  MuSR99 Conference, Les Diablerets: http://www1.psi.ch/~musr99/musr99.html

Quote:

>         You don't have to go to a VAX if you have F77.  On our cluster
> fortr/warn gives:

--
Tim Llewellyn, OpenVMS System Manager, Remarcs Project
MedAS at the BBC, Whiteladies Road, Bristol, UK.

I speak for myself only and my views in no way represent those of
MedAS or the BBC.