Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!ll-xn!cit-vax!tybalt.caltech.edu!walton From: walton@tybalt.caltech.edu (Steve Walton) Newsgroups: comp.lang.fortran,comp.lang.pascal Subject: Re: ALLOCATABLE, ARRAY :: A(:) Message-ID: <3247@cit-vax.Caltech.Edu> Date: Wed, 15-Jul-87 16:57:06 EDT Article-I.D.: cit-vax.3247 Posted: Wed Jul 15 16:57:06 1987 Date-Received: Fri, 17-Jul-87 07:37:20 EDT References: <1215@batcomputer.tn.cornell.edu> <105@anumb.UUCP> Sender: news@cit-vax.Caltech.Edu Reply-To: walton@tybalt.caltech.edu.UUCP (Steve Walton) Organization: Calfornia Institute of Technology Lines: 16 Xref: mnetor comp.lang.fortran:164 comp.lang.pascal:201 In article <672@uhccux.UUCP> bob@uhccux.UUCP (Bob Cunningham) writes: >We have Alliant's Fortran-8x, and version 3.0.14 which is the current >version I'm using supports ALLOCATE. It seems to work as advertised >in the spec, though I haven't any idea how it's actually implemented. Is it actually working fully? Can you send an ALLOCATE'd array to a separately compiled Fortran-77 subroutine in which the corresponding dummy argument is not ALLOCATABLE? Can you DEALLOCATE an array within a subprogram which was ALLOCATE'd by the caller, and vice versa (provided, of course, that the dummy argument is ALLOCATABLE)? If you can, I'd love to see an assembly language dump of the generated code :-). Steve Walton, guest as walton@tybalt.caltech.edu AMETEK Computer Research Division, ametek!walton@csvax.caltech.edu "Long signatures are definitely frowned upon"--USENET posting rules