Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.fortran
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Transfer and variables that don't use all their storage space.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Richard Maine  
View profile  
 More options Apr 9 2007, 11:30 am
Newsgroups: comp.lang.fortran
From: nos...@see.signature (Richard Maine)
Date: Mon, 9 Apr 2007 08:30:26 -0700
Local: Mon, Apr 9 2007 11:30 am
Subject: Re: Transfer and variables that don't use all their storage space.
Print | View thread | Show original | Report this message | Find messages by this author

glen herrmannsfeldt <g...@ugcs.caltech.edu> wrote:
> In Fortran 66, before CHARACTER variables, the standard allowed
> storing of character data, read and written with A format, in
> other types of variables.

A more "interesting" case was "statement label values" (aka addresses)
stored in integer variables with the ASSIGN statement. That's
"interesting" because on some architectures they don't "fit". There have
actually been implementations (several of them) where an integer
variable used for such things had two separate addresses of different
sizes, depending on whether it stored an integer value or a statement
label value.

Brooks:

> > Is that a reasonable contention?

> In general, I don't believe so.  There are some conditions which I
> might wonder about, one is floating point.  On machines with
> unnormalized values, assignment might do normalization.

Assignment is an different question. The question asked about the
transfer intrinsic itself - not about assignment of its result. Those
are *NOT* the same thing. A function result can be used without
assigning it.

> Assignment of 12 byte reals could be done by byte copying, instead of
> loading into a floating point register and storing from there.

Again, the question is not about assignment. The distinction matters.

--
Richard Maine                    | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle           |  -- Mark Twain


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google