On 2021-02-10 15:21:18 CVBruce wrote:
> Eric,
>
> To your point #2. In looking at other implementations of Rexx, I found
> that some implementations note that if you move the write pointer to
> someplace in the existing file, and then write, the file will be truncated
> to that written data. This
Eric,
To your point #2. In looking at other implementations of Rexx, I found that
some implementations note that if you move the write pointer to someplace in
the existing file, and then write, the file will be truncated to that written
data. This led me to the realization that the write poin
Greetings Erich,
Erich Steinböck wrote:
but then: we also have this rexxref paragraph "The write pointer cannot be moved
anywhere within the extent of the file as it existed when the file was opened."
So many errors in one place?
Thus my question: anyone remembers what the intention of all thi
o: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] open() option APPEND
You may be right; I was unable to find a copy of the
pertinent Rexx User's Guide from that period, though
http://www.rexxinfo.org/All%20IBM%20Rexx%20manuals/ALLIBM_1.HTM
purports to provide such.
Lesli
Thanks for clarifying the timeline :-)
Now back to the question:
s~open('append'); s~lineOut('xxx', 1) ignores the line number argument for
lineOut and unconditionally appends
s~open; s~lineOut('xxx', 1) overwrites the first line
This is pretty crazy, as
1) "append" should be default (or not?) fo
Original Message-
> From: J Leslie Turriff [mailto:jlturr...@mail.com]
> Sent: 10 February 2021 16:36
> To: Open Object Rexx Developer Mailing List
> Subject: Re: [Oorexx-devel] open() option APPEND
>
> You may be right; I was unable to find a copy of the
> pertinen
You may be right; I was unable to find a copy of the pertinent Rexx
User's Guide from
that period, though
http://www.rexxinfo.org/All%20IBM%20Rexx%20manuals/ALLIBM_1.HTM
purports to provide such.
Leslie
On 2021-02-10 04:30:20 René Jansen wrote:
> Hi Leslie,
>
> I am sure you mean 1984.
Greetings René,
René Jansen wrote:
I am sure you mean 1984. And then there was still only EXECIO.
Excellent correlation! Indeed EXECIO was the mainframe I/O alternative I could
not recall the name of.
I am thankful,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
___
On Wed, Feb 10, 2021 at 5:31 AM René Jansen wrote:
> Hi Leslie,
>
> I am sure you mean 1984. And then there was still only EXECIO. I have to
> look up when VM/CMS got stream; TSO never had it until now, unless we
> installed a library.
> I will try to find out the timeline.
>
VM/CMS got it 1988,
Hi Leslie,
I am sure you mean 1984. And then there was still only EXECIO. I have to look
up when VM/CMS got stream; TSO never had it until now, unless we installed a
library.
I will try to find out the timeline.
best regards,
René.
> On 10 Feb 2021, at 05:45, J Leslie Turriff wrote:
>
> On
On 2021-02-09 19:02:12 Michael Lueck wrote:
> > Any ideas on how this was meant to be when it was designed?
>
> I never claim to be the best expert at REXX history, however...
>
> On Mainframe, I believe either the Stream concept came much later or still
> is not there at all.
The file I/O
Greetings Erich,
Erich Steinböck wrote:
Any ideas on how this was meant to be when it was designed?
I never claim to be the best expert at REXX history, however...
On Mainframe, I believe either the Stream concept came much later or still is
not there at all.
On OS/2 / Windows / Linux...
Any ideas on how this was meant to be when it was designed?
On Fri, Feb 5, 2021 at 9:14 PM Erich Steinböck
wrote:
> I understand we can open a file for write access in either REPLACE or
> APPEND mode, the latter being the default. Also, rexxpg says "By default,
> LINEOUT appends to an existing
I understand we can open a file for write access in either REPLACE or
APPEND mode, the latter being the default. Also, rexxpg says "By default,
LINEOUT appends to an existing file."
But the open() method description in rexxref describes the APPEND option
with "The write pointer cannot be moved a
14 matches
Mail list logo