NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/os/vms/21770

Text File | 1993-01-23 | 1.6 KB | 37 lines

Newsgroups: comp.os.vms
Path: sparky!uunet!haven.umd.edu!decuac!pa.dec.com!engage.pko.dec.com!nntpd.lkg.dec.com!dbased.nuo.dec.com!quark.enet.dec.com!lionel
From: [e-mail] (Steve Lionel)
Subject: Re: Recursion in FORTRAN
Message-ID: <[e-mail]>
Lines: 24
Sender: [e-mail] (USENET News System)
Reply-To: [e-mail] (Steve Lionel)
Organization: Digital Equipment Corporation, Nashua NH
References: <[e-mail]> <[e-mail]>  <[e-mail]> <[e-mail]>
Date: Fri, 22 Jan 1993 18:34:47 GMT


In article <[e-mail]>, [e-mail] (Terry Poot) writes:
|>(Steve Lionel) writes:
|>>Relax.  The default behavior hasn't changed.   The compiler sort of gives you
|>>a free "SAVE" if it can't determine that you always store a variable before
|>>using it.  But if you use /RECURSIVE, then variables not explicitly SAVEd
|>>won't be.  Also, /RECURSIVE will eliminate guaranteed initialization to zero;
|>>I've heard one customer consider this a feature, so as to ferret out hidden
|>>bugs.
|>
|>Thanks, I was worried. I've also got code that counts on guaranteed
|>initialization. I hadn't thought of that. So as long as I don't use /RECURSIVE,
|>I should be OK, right?
|>

Right on VAX and Alpha AXP, but not on some other platforms, so in the
interest of portability and correctness, put those initializations in!
--

Steve Lionel                    [e-mail]
SDT Languages Group
Digital Equipment Corporation
110 Spit Brook Road
Nashua, NH 03062