On Monday 01 October 2001 08:36 am, Simon Cozens wrote: > On Mon, Oct 01, 2001 at 07:20:56AM -0500, Gibbs Tanton - tgibbs wrote: > > Casting to IV doesn't actually hurt anything (unless there is an > > alignment issue); however, casting to char* is the more idiomatic way of > > doing it. I'll commit this unless Simon says he is going to handle it in > > "The Great Renaming". > > Let me check it on Tru64 first. I'm basically trying to avoid char* in all > its forms, but this is probably OK.
/* Functions for handling strings in native byte format "Native" in this context means the equivalent of "LANG=C": No fancy multi-byte stuff, this is plain old byte-at-a-time. But we don't make any assumptions about what those bytes *mean*. */ 'char' is C's byte type. (Well, most likely, unsigned char.) To avoid char * where void * is warranted is good. To avoid char * where char * is warranted is bad. If you're afraid of causing mental programmer problems with byte-wise data that isn't character data, then typedef u_char as byte. -- Bryan C. Warnock [EMAIL PROTECTED]
