I don't know. But repeatedly setting $X=0 solved the problem.
On 8/25/05, smcphelan [EMAIL PROTECTED] wrote:
Would it have something to do with flushing the buffers?
- Original Message -
From: Greg Woodhouse [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent:
-members@lists.sourceforge.net
Sent: Friday, August 26, 2005 7:13 AM
Subject: [Hardhats-members] Re: Binary Read/Writes
I don't know. But repeatedly setting $X=0 solved the problem.
On 8/25/05, smcphelan [EMAIL PROTECTED] wrote:
Would it have something to do with flushing the buffers
. It may be as simple as opening the device with NOWRAP.
- Original Message -
From: Kevin Toppenberg [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Friday, August 26, 2005 7:13 AM
Subject: [Hardhats-members] Re: Binary Read/Writes
I don't know
implementation's
I/O features.
- Original Message -
From: Kevin Toppenberg
To: hardhats-members@lists.sourceforge.net
Sent: Friday, August 26, 2005 10:18 AM
Subject: [Hardhats-members] Re: Binary Read/Writes
Are all these NOWRAP type specifiers non-implementation specific?
I.e. standard
Toppenberg
To: hardhats-members@lists.sourceforge.net
Sent: Friday, August 26, 2005 10:18 AM
Subject: [Hardhats-members] Re: Binary Read/Writes
Are all these NOWRAP type specifiers non-implementation specific?
I.e. standard mumps?
Kevin
to read the documentation if you want to understand a
given
implementation's I/O features.
- Original Message -
From: Kevin Toppenberg
To: hardhats-members@lists.sourceforge.net
Sent: Friday, August 26, 2005 10:18 AM
Subject: [Hardhats-members] Re: Binary Read/Writes
.
- Original Message -
From: Greg Woodhouse [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Friday, August 26, 2005 1:10 PM
Subject: Re: [Hardhats-members] Re: Binary Read/Writes
That's why VistA applications are not allowed to OPEN or CLOSE devices
on their own
, 2005 7:13 AM
Subject: [Hardhats-members] Re: Binary Read/Writes
I don't know. But repeatedly setting $X=0 solved the problem.
On 8/25/05, smcphelan [EMAIL PROTECTED] wrote:
Would it have something to do with flushing the buffers?
- Original Message -
From: Greg
On Fri, 2005-08-26 at 13:08 -0500, Jim Self wrote:
No, device parameters are implementation specific.
NOWRAP does work for GT.M, sorry I forgot to mention it the first
time.
The best online reference for Standard MUMPS features is Ed de Moel's
MUMPS by Example -
I gave a link to it
Hurrah! I had just built a hex browser and was looking at the data at
different steps. I figured that it was a problem at the writing
level, and that it was adding #10 (a linefeed).
Then I read your post and it all made sense. I still have a very hard
time remembering that M IO keeps track of
So, there is effectively a W ! whenever $X reaches the maxiumum record
size?
--- Kevin Toppenberg [EMAIL PROTECTED] wrote:
Hurrah! I had just built a hex browser and was looking at the data
at
different steps. I figured that it was a problem at the writing
level, and that it was adding
The IO system apparently keeps in its mind the width of the screen.
When attempts to write off the right hand side of the Screen are
encountered, it writes a line feed to the IO stream.
Apparently in the case of a file to a disk, it sets this screen
width to 32,768. After that many bytes, it
12 matches
Mail list logo
