On 3/5/06, Stewart Stremler <[EMAIL PROTECTED]> wrote:
> begin quoting John H. Robinson, IV as of Sun, Mar 05, 2006 at 12:34:38PM
> -0800:
> > Stewart Stremler wrote:
> [snip - emphasis of "legal character"]
> > > And nulls. Don't forget nulls.
> >
> > Outside the scope. Nulls are not allowed in filenames.
>
> Baloney. It's such an arbitrary restriction. It's a legal ASCII value;
> surely it should be allowed in a filename, by your own argument.
>
> > > > What is truly evil is disk-editing a solidus into a filename.
> > > There have been systems that did not use spaces for tokenization; they
> > > are generally (in my opinion) more difficult to use; this is reflected
> > > in the MSDOS use of / as an option indicator -- and all the fun that
> > > results from that. And fortran had the worst of both worlds: mandatory
> > > leading whitespace and optional whitespace everywhere else.
> > It is just a
> > different way of doing it. How you describe Fortran, though, just sounds
> > to be complete brain-death.
>
> IFI.EQ.1GOTO10
>
Leading to the classical Fortran typo, that crashed a missile test flight:
DO 10 I = 1.10
By Fortran parsing rules, rather than being the setup for a loop, this
declared a variable named DO10I and set it equal to the value 1.10.
Neat, eh?
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
