On Thu, Apr 21, 2005 at 03:56:50PM +0100, Ian Lynagh wrote: > > That shouldn't be necessary -- all the locales in Debian agree with C > > on ASCII-only text. > > Ah, that would be convenient. I've just done a quick test and they all > seem OK except vi_VN.TCVN (both with latest CVS and the release):
There was a small bug in Hugs, but I think this locale is broken (#305831). > > > cpphs currently accepts 8-bit > > > chars in filenames being #included, as does cpp; maybe you will argue > > > that making use of that is foolish, but nevertheless I think I would > > > rather drop the ability to "compile" with hugs in order to keep its > > > behaviour consistent. > > > > Do you mean #include's in the source file, which is read in text mode? > > It is currently, but with new hugs I think it should really be being > read in binary mode and cpphs then do its own line ending magic. I would have thought that cpp input was text -- does cpphs really do anything with crlf's? Anyway, full compatibility with a GHC-compiled version isn't possible (which was you point) so I guess dropping the cpphs/hugs combination seems reasonable, as you have ghc or nhc98 on all archs. > > It's a tradeoff, I just don't think it's a grave bug. > > The severity of Debian bug 299702 is just the mechanism used to keep the > package out of testing. I meant that I appreciate that you've been worried about the filename issue for some time, but that it wouldn't justify keeping Hugs out on its own. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
