Dave Larrington said:
Depends on your version of F77 thobut. I am engaged in doing Stuff with VMS
FORTRAN on a daily basis and while some of the ancient legacy code /does/
use COMMON blocks, most of it doesn't. And it allows all sorts of creative
variable names. As to this memory allocation wossname, surely it's the job
of the operating system to do that?
I learned computer programming with VAX FORTRAN and it is indeed miles
better than pure F77, but note that VAX FORTRAN isn't FORTRAN 77, it's a
considerably enhanced superset (with a lot of features that ended up in
F90 IIRC, but it's been a while so ICBW). Similarly, compare Visual
BASIC to BASIC and Turbo Pascal to Pascal.
FORTRAN 77 is a standard (ANSI?) language definition, and a complier
either supports it or it doesn't.
The memory allocation is indeed the OS's job, but how much to ask for
isn't always known in advance of running or (especially) compiling. If
I write a hack to wangle a file, for example, in standard F77 there's no
way I can find out the size of the file on the fly and /then/ allocate
enough, and only enough, memory to deal with it. And since I might be
dealing in files of several hundred Mb with 3D image stacks, that's a
bit of a waste of system resources!
Quoted message said:Sadly, when our women and their jobs go to India in the not-too-distant
future I will no longer have a VMS system with which to play.
I always got on well with the VAXen I used. Shame the system architect
carried its naturally fragmenting file system onto his subsequent job at
Microsoft though :-(
Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net [email hidden] http://www.dundee.ac.uk/~pjclinch/