Are you making this more difficult that it has to be? (I can't *imagine* you doing that! :-) )
I don't know about the big/little endian issues. I am not planning to store two-byte words, so I don't think this comes into play. I will just store the bytes as they come in the stream. And I don't want to use a GT.M unique solution, as that will greatly limit potential use by others. Kevin P.S. I read that using this syntax: use IO:(NOTERMINATOR) is supposed to make the stream not stop at "terminator" characters. But it doesn't seem to work for me yet. Kevin On 8/21/05, Chris Richardson <[EMAIL PROTECTED]> wrote: > Kevin; > > There is only a single data-type in MUMPS, strings. What you are doing > is a fixed length buffer read of characters (real characters or binary > data). You are opening up a big bag of issues which the MDC argued over > for > decades. If you are talking about binary, are you talking about big-endian > or little-endian representation (what do the bits mean?). By dealing in > characters, we don't have to worry about byte order per word. Now some > implementations did provide tools for doing these operations (most notable > was Micronetics (now InterSystems). I believe that GTM has some of these > same tools. They also have the thinnest binding with the underlying > operating system, so poking out to do this type of operation is pretty > simple in GT.M. > ------------------------------------------------------- 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
