HP3000-L Archives

April 1997, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Mon, 21 Apr 1997 12:12:13 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Michael writes:

> The perfect solution would be for HP's implimentation of POSIX to allow all
> these special characters :-)

Although I agree with the idea behind the above, I must point out:

   MPE/iX supports the *POSIX* specification of valid filename
   characters.  *POSIX* doesn't allow very many special characters,
   although most *UNIX* implementations do!

Still, technicalities (and defense of MPE's POSIX implementation) aside,
I've been lobbying for MPE to allow many more special characters
in filenames (indeed, all but null).

However, Jeff Vance of HP has asked some hard questions about this...
perhaps we can get him to lead a discussion on it?  ([log in to unmask])
E.g., the interaction between CI commands and newly allowed
characters ... if "@" is allowed, how does the CI interpret:
   :purge ./foo@
does it purge the file "foo@", or all files beginning with "foo"?

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2