Date: Tue, 19 Sep 1995 20:28:25 -0500 (CDT) From: peter@taronga.com (Peter da Silva) To: terry@lambert.org (Terry Lambert) Cc: peter@taronga.com, hackers@freebsd.org Subject: Re: Policy on printf format specifiers? Message-ID: <199509200128.UAA13444@bonkers.taronga.com> In-Reply-To: <199509192020.NAA10542@phaeton.artisoft.com> from "Terry Lambert" at Sep 19, 95 01:20:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > >Rendering the file length meaningless and requiring the use of record > > >oriented file systems with variant length records to handle data from > > >fix length input fields from user interaction screens. > > And this claim is just weird. This is an application issue... file systems > > have nothing to do with it. If the only things you feed into the kernel > > are multibyte character strings, you don't need any of this. > Suprise. Software engineers write applications. The software component known as a file system is a fairly simple application. It doesn't need to even consider the meaning of any multibyte character, it has to recognise when a "/" is part of a character as opposed to being a complete character itself, by looking at the high bit of the previous byte. > 8-). The complaint isn't > that you can't work around what is effectively a loss of information, but > that you have to do so. What information loss is that?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509200128.UAA13444>