That's why VistA applications are not allowed to OPEN or CLOSE devices on their own, and are not allowed to use builtins like $I and $P.
The MDC may have thought that leaving these types of things up to the vendors was the right thing to do, but I believe it was a mistake. Something so basic as writing binary data to a file should not require implementation specific code. --- Kevin Toppenberg <[EMAIL PROTECTED]> wrote: > so in OPEN^%ZISH, where I see such parameters, does that mean that > this is one of those areas that gets customized for the differenct M > environments? Must be so. > > Kevin > > > On 8/26/05, Maury Pepper <[EMAIL PROTECTED]> wrote: > > NO! Not at all. This was an area left to the implementor. GT.M's > I/O > > parameters look similar to those from VMS (and thus, DSM.) MSM > copied > > DSM-11 which looks nothing like VAX DSM. DTM and others are all > different. > > You HAVE to read the documentation if you want to understand a > given > > implementation's I/O features. > > > > > > ----- Original Message ----- > > From: "Kevin Toppenberg" > > To: <[email protected]> > > 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 === Gregory Woodhouse <[EMAIL PROTECTED]> "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- Antoine de Saint-Exupery ------------------------------------------------------- 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
