Path: utzoo!attcan!uunet!jarthur!usc!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!l.cc.purdue.edu!cik
From: cik@l.cc.purdue.edu (Herman Rubin)
Newsgroups: comp.lang.misc
Subject: Re: Efficient Fortran
Summary: So put in longer integers.
Message-ID: <2378@l.cc.purdue.edu>
Date: 19 Jul 90 12:05:03 GMT
References: <1990Jul3.194348.21178@msuinfo.cl.msu.edu> <9595@brazos.Rice.edu> <1991@key.COM>
Organization: Purdue University Statistics Department
Lines: 23

In article <1991@key.COM>, sjc@key.COM (Steve Correll) writes:
> In article <138349@sun.Eng.Sun.COM>, lm@snafu.Sun.COM (Larry McVoy) writes:
> > I have before me "Programmers Guide
> > to Fortran 90" which contains things, such as pointers, that make me wonder
> > if this is going to make fortran an uninteresting language.
> 
> In article <2306@l.cc.purdue.edu>, cik@l.cc.purdue.edu (Herman Rubin) writes:

			........................

> Regarding the merits of assigned GOTO, consider an architecture where the
> address of an instruction cannot in fact be stored in an INTEGER variable
> (because, for example, an address has 64 bits whereas an integer has 32).

Wither put in longer integers, or use an integer array, or something 
equivalent.  If you cannot do this, consider the implementation inadequate.

The purpose of a language should be to enable programmers, not to disable
them, to get things done.
-- 
Herman Rubin, Dept. of Statistics, Purdue Univ., West Lafayette IN47907
Phone: (317)494-6054
hrubin@l.cc.purdue.edu (Internet, bitnet)	{purdue,pur-ee}!l.cc!cik(UUCP)