On Tue, Jul 08, 2003 at 11:04:27AM -0400, Alexander R. Pruss wrote:
> 1. This looks to me like it's checking for all two-byte length characters,
> not just CRLF. This surely isn't correct behavior, because it will allow
> line-breaking at any two-byte length character.
I think you're right...
> 2. Thus, how do we check that the character is indeed CRLF? What is the
> two-byte encoding of CRLF?
In this other program which I'm working on, here is what I do (not
saying it anymore right, but one possibility)
static const Char CRLF[] = { 0x0D, 0x0A, 0x00 };
[..]
while ( ( newLinePtr = StrStr( bufferPtr, CRLF ) ) != NULL ) {
StrNCopy( thisLine, bufferPtr, newLinePtr - bufferPtr );
(do something with thisLine)
bufferPtr = newLinePtr + 2;
}
> 3. And why should there be a CRLF in the record given that we have
> function 0x38 instead?
Why would there be a CRLF in html if there's a <br>/<p> tag instead?
--
Adam McDaniel
Array.org
Calgary, AB, Canada
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
