Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!wuarchive!psuvax1!rutgers!cmcl2!lanl!cochiti.lanl.gov!jlg
From: jlg@cochiti.lanl.gov (Jim Giles)
Newsgroups: comp.lang.fortran
Subject: Re: Is that a bug? (please answer by e-mail)
Message-ID: <24234@lanl.gov>
Date: 22 May 91 18:41:26 GMT
References: <PRZEMEK.91May22123736@rrdstrad.nist.gov>
Sender: news@lanl.gov
Organization: Los Alamos National Laboratory
Lines: 20

In article <PRZEMEK.91May22123736@rrdstrad.nist.gov> przemek@rrdstrad.nist.gov (Przemek Klosowski) writes:

|> [...]
|> ::::::::::::::                             ::::::::::::::                 
|> tst1.f                                     tst2.f                         
|> ::::::::::::::                             ::::::::::::::                 
|>         common /aa/ aa1, aa2                       subroutine tst2        
|>         data aa1 /1.0/                             common /aa/ aa1, aa2   
|>         call tst2                                  data aa2 /2.0/         
|>         type *, aa1, aa2                           aa1=1.01               
|>         end                                        end

The Fortran standard allows data loading of objects in a named common
block only within BLOCK DATA modules.  Blank common may not be data
loaded at all.  Most _quality_ implementations let you get away with 
it anyway.  Apparently, you've hit an implementation with no quality.
Most UNIX Fortran implementations are junk - but even most of those
allow data loading of common.

J. Giles