On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:
sys.stdout.writelines(sys.stdin.readlines())
sys.stdout.writelines(sys.stdin.readlines())
Some interesting semantics going on there. How do you continue reading
after encountering EOF? How does it reset the EOF condition to let you get the second lot of data?
Normally, once an open file gets to EOF, it stays in that state until fseek(2) (or equivalent) is called.
On 6/16/2025 9:28 PM, Lawrence D'Oliveiro wrote:
On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:
sys.stdout.writelines(sys.stdin.readlines())
sys.stdout.writelines(sys.stdin.readlines())
Some interesting semantics going on there. How do you continue reading
after encountering EOF? How does it reset the EOF condition to let you
get
the second lot of data?
Normally, once an open file gets to EOF, it stays in that state until
fseek(2) (or equivalent) is called.
You put 3 decks of punched cards in the card reader.
One with the python program and two with data.
When it hit EOF on the first data deck then readlines()
stop, but the next readlines() start on the next data deck.
I did not know that it would work. But I tried and
it did work.
sys.stdout.writelines(sys.stdin.readlines()) sys.stdout.writelines(sys.stdin.readlines())
On 6/16/2025 9:28 PM, Lawrence D'Oliveiro wrote:
On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:
sys.stdout.writelines(sys.stdin.readlines())
sys.stdout.writelines(sys.stdin.readlines())
Some interesting semantics going on there. How do you continue reading
after encountering EOF? How does it reset the EOF condition to let you get >> the second lot of data?
Normally, once an open file gets to EOF, it stays in that state until
fseek(2) (or equivalent) is called.
You put 3 decks of punched cards in the card reader.
On 2025-06-16, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 6/16/2025 9:28 PM, Lawrence D'Oliveiro wrote:
On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:
sys.stdout.writelines(sys.stdin.readlines())
sys.stdout.writelines(sys.stdin.readlines())
Some interesting semantics going on there. How do you continue reading
after encountering EOF? How does it reset the EOF condition to let you get >>> the second lot of data?
Normally, once an open file gets to EOF, it stays in that state until
fseek(2) (or equivalent) is called.
You put 3 decks of punched cards in the card reader.
The fact VMS supported punched card devices always amuses me as it
clearly shows VMS with one foot in a long-obsolete era and the other
foot in a more modern era.
Did punched card support ever make it to Alpha ?
BTW, did VMS ever have paper tape reader (and/or writer) support ?
BTW, did VMS ever have paper tape reader (and/or writer) support ?
Simon.
The fact VMS supported punched card devices always amuses me as it
clearly shows VMS with one foot in a long-obsolete era and the other
foot in a more modern era.
It shouldn't at all be a surprise!
They were still in high-end use in 2001!
On 2025-06-16, Arne Vajhøj <arne@vajhoej.dk> wrote:8< snip 8<
On 6/16/2025 9:28 PM, Lawrence D'Oliveiro wrote:
On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:
The fact VMS supported punched card devices always amuses me as it8< snip 8<
clearly shows VMS with one foot in a long-obsolete era and the other
foot in a more modern era.
The fact VMS supported punched card devices always amuses me as it
clearly shows VMS with one foot in a long-obsolete era and the other
foot in a more modern era.
Did punched card support ever make it to Alpha ?
BTW, did VMS ever have paper tape reader (and/or writer) support ?
I'm not familiar with any formal support for paper tape readers within VAX/VMS ...
On 6/17/25 11:07, Simon Clubley wrote:
The 11/780 had a 20mA current loop DZ11-C multiplexer so an ASR-33
BTW, did VMS ever have paper tape reader (and/or writer) support ?
Simon.
teletype could be attached and that has a paper tape reader/punch.
On a more serious note: Thanks, I didn't realise there was a 20mA
current loop option for VAX systems.
I'm pretty sure there was a 20mA option for connectivity on the VT100
On Thu, 19 Jun 2025 10:43:26 -0400, Robert A. Brooks wrote:
I'm pretty sure there was a 20mA option for connectivity on the VT100
Optional, according to a user guide I just checked.
On 6/17/2025 2:07 PM, Simon Clubley wrote:
On 2025-06-16, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 6/16/2025 9:28 PM, Lawrence D'Oliveiro wrote:
On Mon, 16 Jun 2025 15:15:39 -0400, Arne Vajhøj wrote:
sys.stdout.writelines(sys.stdin.readlines())
sys.stdout.writelines(sys.stdin.readlines())
Some interesting semantics going on there. How do you continue reading >>>> after encountering EOF? How does it reset the EOF condition to let
you get
the second lot of data?
Normally, once an open file gets to EOF, it stays in that state until
fseek(2) (or equivalent) is called.
You put 3 decks of punched cards in the card reader.
The fact VMS supported punched card devices always amuses me as it
clearly shows VMS with one foot in a long-obsolete era and the other
foot in a more modern era.
Did punched card support ever make it to Alpha ?
You would need physical connectivity and a driver.
A quick googling on VAX punched card reader points to
CR11 card reader connected to a UNIBUS card.
So I doubt it.
But DCL still got $ DECK and $ EOD. :-)
BTW, did VMS ever have paper tape reader (and/or writer) support ?
No idea.
Arne
On 6/19/2025 8:09 AM, Simon Clubley wrote:
On a more serious note: Thanks, I didn't realise there was a 20mA
current loop option for VAX systems.
I'm pretty sure there was a 20mA option for connectivity on the VT100
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 506 |
Nodes: | 16 (3 / 13) |
Uptime: | 130:22:36 |
Calls: | 9,944 |
Calls today: | 5 |
Files: | 13,819 |
Messages: | 6,351,443 |
Posted today: | 2 |