From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c4cb2c432feebd9d
X-Google-Thread: 1094ba,c4cb2c432feebd9d
X-Google-Attributes: gid103376,gid1094ba,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!opentransit.net!newsfeed.icl.net!colt.net!peernews3.colt.net!news0.de.colt.net!newsfeed.r-kom.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: =?ISO-8859-1?Q?Jan_Vorbr=FCggen?= <jvorbrueggen@not-mediasec.de>
Newsgroups: comp.lang.ada,comp.lang.fortran
Subject: Re: Ada vs Fortran for scientific applications
Date: Mon, 29 May 2006 14:56:50 +0200
Organization: MediaSec Technologies GmbH
Message-ID: <4e09bgF1cdqssU2@individual.net>
References: <mubcg.13522$fb2.853@newssvr27.news.prodigy.net>
 <4dd87pF18ot14U1@individual.net> <447207D6.3010408@cits1.stanford.edu>
 <4dg101F17acafU1@individual.net> <44730df4$1@news.meer.net>
 <4diimsF1b0c25U1@individual.net>
 <8V_cg.155757$eR6.70498@bgtnsc04-news.ops.worldnet.att.net>
 <646dnfYoKul8MOnZnZ2dnUVZ_tydnZ2d@comcast.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net EaACQLboMoXwBy4t0ylpXgwahl0vcUIQ7V0H9LAgtsE8OdZwyu
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: de-DE, de, en-us, en
In-Reply-To: <646dnfYoKul8MOnZnZ2dnUVZ_tydnZ2d@comcast.com>
Xref: g2news2.google.com comp.lang.ada:4579 comp.lang.fortran:10423
Date: 2006-05-29T14:56:50+02:00
List-Id: <comp.lang.ada>

> OK, but say for a certain program it is more efficient to store a 
> complex array with all the real parts followed by all the imaginary 
> parts, and the compiler figured this out.  The "as if" rule would work 
> only if there was no other way for the program/programmer to discover 
> the change.  If the array was in COMMON, EQUIVALENCEd, or passed to an 
> external routine, this optimization most likely couldn't be done.
> Without any legal way to view the storage association, it would seem 
> possible to do it.

Precisely what I was thinking. So historic baggage is weighing Fortran down
in this particular case.

	Jan