I'm not talking about D[r]OS[s]. I'm talking about POSIX-conforming operating systems, i.e. *real* operating systems. ;-) Specifically, we're talking about writing shell scripts for such operating systems. We're not talking about portability to other operating systems.
I've seen all kinds of broken crap in my years of programming and have rewritten some and written work arounds for so many others. Even when the software claims to conform to some standard, it often doesn't.
Somebody (was it Tannenbaum?) said, "The great thing about standards is there are so many to choose from." I'd like to add that the great thing about any given standard is that there are so many different ways to interpret it.
Derek Martin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jan 21, 2003 at 12:16:51PM -0500, Derek Martin wrote:In the real world, you will run into these kinds of problems... It
does not matter that spaces are allowed in filenames; practical
considerations may make them difficult or impossible to use.
And it may also be worth noting that on Windows versions <= Windows
ME (i.e. DOS), you can't access files with spaces in their names on
the command line. It is possible to create such files
programmatically, but you have no hope of accessing them from the
command line. Windows NT and subsequent releases based on it do not
have this limitation...
- -- Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0xDFBEAD02
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+LYP4HEnASN++rQIRAvBIAKCTFEl/Lrs8or+HiJMpDFiib7EEGQCglx4t
MmuN1oRhDNK6oob8Tq2CbWs=
=c+mW
-----END PGP SIGNATURE-----
_______________________________________________
gnhlug-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
_______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
