this put me in mind of bind8. the code below i think i wrote in 1993.
clearly i could have used isascii() but my feeling at the time was that
network data should be measured in absolute terms whereas ctype seemed
relative (to the local charset). this all comes from dns not having a
well defined presentation layer. but if you wanted to change m_getfld()
to say (x == 0x20 || x == 0x0a || x == 0x09) instead of isspace() then
you would likely not break much. (unless you're on a system where
getchar() is inserting 0x0d after every actual 0x0a it finds in the
stream, in which case all bets are off.)
in e-mail headers, a space is what rfc822 says it is, not what POSIX
says it is.
So, just curious ... is this still what you do for bind9? I'm with you,
though ... a space has a specific meaning according to rfc822 and doesn't
necessarily match up with what isspace() is.
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers