Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!mcnc!ecsgate!ecsvax!uncw!session From: session@uncw.UUCP (Zack C. Sessions) Newsgroups: comp.lang.fortran Subject: Re: dynamic storage Message-ID: <1053@uncw.UUCP> Date: 7 Mar 91 05:17:56 GMT References: <38747@netnews.upenn.edu> <1050@uncw.UUCP> Organization: Univ. of North Carolina at Wilmington Lines: 23 khb@chiba.Eng.Sun.COM (Keith Bierman fpgroup) writes: >In article <1050@uncw.UUCP> session@uncw.UUCP (Zack C. Sessions) writes: > an exercise in Data Structures. What some do (if both a C AND a FORTRAN > compiler is available) is use C subroutines to perform the dynamic >C is irrelvant. It is really an OS service issue. On many systems >(VAX, Sun, CDC, etc.) you can do it in extended Fortran. You may >prefer BLISS, Cybil, assembler or old Norse ..... >Keith H. Bierman kbierman@Eng.Sun.COM | khb@chiba.Eng.Sun.COM I did not imply that C was _required_ to do dynamic memory allocation. Certainly other languages do as well, most notably PL/1 with it's ALLOCATE statement. I was merely pointing out an alternative since dynamic memory allocation is NOT part of standard FORTRAN, but MAY be available with some implementations of *Extended* FORTRAN. Oh, and since I *did* suggest C, it may be obvious that I would prefer C. Zack Sessions session@uncw.UUCP