Re: Automatic based variables

Joe,

How does %open behave strangely? I just did a little test (added two
procedures to a mainline program; one for opening and one for closing;
called the opening one in case of page up and the closing one in case of
page down; opened the file in the mainline when it was not open; stepped
through the whole thing in debug mode) and did not find anything strange.

Joep Beckeringh


----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, November 21, 2003 3:51 PM
Subject: RE: Automatic based variables


> > From: Joep Beckeringh
> >
> > But what bizarre reason might that be? If the compiler would allocate
> > storage, that storage would be unreachable once the basing pointer is
> set.
>
> I can think of no good reason to allocate storage.  However, the
> compiler doesn't always do things that make sense to me.  For example,
> if you have a module where you have both a mainline and called
> procedures, %OPEN BIF acts strangely.  There's no good reason for it to
> act the way it does.  So I've learned to take nothing for granted, and I
> was just trying to make sure of my supposition.
>
> Joe