Are all these NOWRAP type specifiers non-implementation specific? 
I.e. standard mumps?

Kevin


On 8/26/05, Maury Pepper <[EMAIL PROTECTED]> wrote:
> It is a common (but not standard) feature with M that a device has a "width"
> attribute which can be set somewhere.  After writing <width> characters, the
> equivalent of W ! is inserted to start a new line.  This is "line wrap"
> controlled by the M device driver instead of the device.  In MSM, if width
> is set to zero, then the feature is disabled.  I don't know how GT.M
> controls this feature or if it can be disabled -- but I suspect it's
> documented.  It may be as simple as opening the device with "NOWRAP".
> 
> 
> ----- Original Message ----- 
> From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> To: <[email protected]>
> 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?
> >> 
> >> ----- Original Message ----- 
> >> From: "Greg Woodhouse" <[EMAIL PROTECTED]>
> >> To: <[email protected]>
> >> Sent: Thursday, August 25, 2005 3:34 PM
> >> Subject: Re: [Hardhats-members] Binary Read/Writes
> >> 
> >> 
> >> I don't really understand this. What effect does setting $X to 0 have
> >> in this case? 
> >> 
> >> --- Jim Self <[EMAIL PROTECTED]> wrote:
> >> 
> >> > Kevin wrote:
> >> > >Every 32,768 bytes ($8000 hex), it adds one extra byte (!)
> >> > >
> >> > >I haven't figured out yet if this is on the read phase or write
> >> > phase.
> >> > 
> >> > One way to prevent that is to SET $X=0 after every WRITE, or do it at
> >> > least once before it
> >> > reaches that value.
> >> > 
> >> > ---------------------------------------
> >> > Jim Self
> >> 
> >> 
> >> 
> >> 
> >> -------------------------------------------------------
> >> SF.Net email is Sponsored by the Better Software Conference & EXPO
> >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> >> Agile & Plan-Driven Development * Managing Projects & Teams * Testing &
> QA
> >> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> >> _______________________________________________
> >> Hardhats-members mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >>
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams * Testing &
> QA
> > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Hardhats-members mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Hardhats-members mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to