Bernie wrote:
>
> CLarence wrote:
> >There otta be a law against lower case on the commandline. <G>
>
> IMHO there should be a law against making programs that care about case.
Hi Bernie;
I think you missed my point.
If I tell you a commandline switch is /l, what am I saying ?
This is a problem in Michael's documentation of JPEG args.
A document should be PERFECTLY clear. To do that the switches must be
presented in upper case.
Remember, what the reader sees depends on the font he is using.
"l","1", and "I" can look each look very different to the reader and writer.
And usually the reader doesn't see them side by side as above to help him
make a guess. <G>
> but there's a reason why we don't write in CAPS all the time - it doesn't
> look good. Assuming low case would make it look better. Besides, I've
> always thought of my files as lower case anyway.
This is a matter of how you learned. I think UPPERcase looks better on
the commandline and in source code. When I started writing code, uppercase
is all there was.
I think of MY files in uppercase. <G>
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
