Re: proposed Eistring interface
"Stephen J. Turnbull" wrote:
>>>>> "Ben" == Ben Wing <ben(a)666.com>
writes:
Ben> i will be implementing piece by piece, as necessary. here's
Ben> what i have so far, and i'd like comments:
What are these "C strings where non-ASCII characters are illegal"? I
thought a C string (as defined by <string.h>) was a char[],
with the length determined by the position of the first ASCII NULL.
Do you mean that, eg, trying to feed it an ISO-8859-1 string will
cause an abort with error-checking? How about control characters (C1,
obviously, but C0, too)? These are all legal characters in both the
current leading-byte representation and any Unicode-based
representation.
you are confused. "c string" is simply one special case of an external
representation.
eicpy_c(ei, c_string) is exactly the same as eicpy_ext(ei, c_string, Qbinary),
other than
this check. This is defined only to make it easier to use literal ASCII strings,
which is
going to be extremely common. If the string has any non-ASCII characters in it,
they
need to explicitly specify the encoding -- hence the restriction.
If the SOURCE was an ei_string and the DESTINATION a C string, that
restriction might make sense. Is this just a typo?
But I really don't see where you're going with that kind of
restriction. Which byte values make sense in a given char[] object is
going to depend very much on context, and I don't think that belongs
at this level.
Cf:
eicpy_c (eistr, c_string):
... from an ASCII null-terminated string. Non-ASCII characters in
the string are *ILLEGAL* (read abort() with error-checking defined).
eicpy_c_len (eistr, c_string, len):
... from an ASCII string, with length specified. Non-ASCII characters
in the string are *ILLEGAL* (read abort() with error-checking defined).
BTW, your mailer's (I assume you are cutting and pasting from source
files with what I would consider very long lines for text)
not true, the only thing i pasted in came from a .c file, wrapped at 75 chars per
line. the rest was typed in.
wrapping
behavior leaves a LOT to be desired.
sorry, i am using netscape 4.7 and i'm not sure i have much control over this.
could you please send me back one of my messages as an attachment in text/plain
(i.e. not marked as a mail message, so that Netscape doesn't try to wrap it on
input)? i'm really not sure what my messages look like to others because of all
the futzing that Netscape does.
probably i should use vm, but in a great number of ways it just totally sucks in
comparison to netscape. (can't handle large folders well, is really slow in
general, doesn't provide its own filtering mechanism, i don't like its ui,
doesn't
seem to handle multiple folders well, etc.) perhaps i'm missing something here -- i
know that some of vm's annoyances can be fixed by just fiddling with some variables
(how come it doesn't just work right out of the box???) and i haven't used it for
awhile, so it may have totally changed and my complaints may not be valid.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also http://www.666.com/ben/typing.html.