From: Akim Demaille <[EMAIL PROTECTED]> Date: 26 Feb 2000 08:44:20 +0100 [ About the 8-bit bug on Ultrix ] Finally, I'd like to understand how this turns out to be a malign bug. I mean, I do see the 8th bits are set while they should not, but if such a bug could have leaved inside a shell, it probably means that the shell itself doesn't care about the 8th bit, doesn't it? So where did it *hurt*, where did that 8th bit set made a difference? What wrong behavior appeared? When the Ultrix /bin/sh reads the config.cache file, it does discard the 8th bit. So this bug almost certainly does not hurt, provided you always read config.cache with the same shell, and provided you don't accidentally look at it manually. Ian
- Re: config.cache considered harmful Ian Lance Taylor
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Ian Lance Taylor
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Ian Lance Taylor
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Ian Lance Taylor
- Re: config.cache considered harmful Paul Eggert
- Re: config.cache considered harmful Ian Lance Taylor
- Re: config.cache considered harmful Akim Demaille
- Portable programming (was: config.cache consider... Ian Lance Taylor
- Portable programming (was: config.cache consider... Russ Allbery
- Re: config.cache considered harmful Martin Buchholz
- Re: config.cache considered harmful Didier Verna
- Re: config.cache considered harmful Felix Lee
- Re: config.cache considered harmful Harlan Stenn
- Re: config.cache considered harmful Felix Lee
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Martin Buchholz
- Re: config.cache considered harmful Akim Demaille
- Re: config.cache considered harmful Martin Buchholz