Jeff makes the following comment in response to Stan's comments about
allow an escape character within all filenames:

>It does, however, allow us to keep the wall between classic MPE and POSIX
>low.

This in and of itself is a "pretty good thing" given the comments over the past
few months with regard to POSIX smoothing and making POSIX fit better into the
MPE environment (and vice versa).

>This is an important question, but I would like to validate the assumption
>that existing MPE interfaces, not used by the POSIX environment, need to
>support extended characters and thus an esacpe character?

Actually, there are valid reasons to allow this from MPE applications. For
example, I use files in the HFS space that are similarly named to something in
the MPE name space for keeping certain bits of data - just like Jumbo Data Sets
are done for TurboIMAGE. This is an MPE application, not a POSIX application.
Further, including these special characters in the name allows much more
flexibility (which can be translated into better usability for the users) in the
choice and management of these file objects.

Regards,


M.