"Gary E. Miller" <[email protected]> writes: > Yo Greg! > >> But that still leaves the locale problem. I was thinking more like: > > This is the part I worry about, from the Linux "man isacii" > > These functions check whether c, which must have the value of > an unsigned char or EOF, falls into a certain character class > according to the specified locale. The functions without the "_l" > suffix perform the check based on the current locale. > > I'm worried the "current locale" thing.
I don't see why you need to bite off worrying. Just cast to unsigned character and let the standards-required functions work. What gpsd probably should do, is to distinguish between text in the user's locale, and text from protocols, figure out locale from those protocols, and have a way to have the C locale active while processing protocol text. But that's not about this particular usage -- it's larger. I had not heard of isascii_l(). Is that specified by C99 or POSIX?
