The key word (not the keyword) here is "encoded". Fileman actually
provides utilities for hexadecimal encoding that I've found useful on
more than one occasion. There are really two issues here: whether the
M implementation can handle binary data (not necessarily), and
whether applications can work with binary data. In the latter case,
there is the problem that M programmers have a propensity for using
sentinel values like "^" to delimit data items, but the first problem
is much more serious.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"The most incomprehensible thing about
the world is that it is at all comprehensible."
--Albert Einstein (1879-1955)
On Aug 21, 2005, at 1:26 PM, Ruben Safir wrote:
On Sun, 2005-08-21 at 12:57 -0700, Chris Richardson wrote:
Ah, but how big is a character? MUMPS deals in characters
reguardless of
the number of octets required to represent it.
1Octet = 8 bits
Ascii - 1 octet/character
Unicode, Kanji,Katakana,etc - 2 octets/character
ISO-10646 - 4octets/character
In terms of storing and retrieving data, it shouldn't matter. We've
been dealing with 7 bit encoded attachments for a decade in email.
Ruben
-------------------------------------------------------
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
