Proposal: #ModuleNameCharacters

mark.reinhold at oracle.com mark.reinhold at oracle.com
Fri Dec 9 16:39:16 UTC 2016


2016/12/8 18:12:10 -0800, david.lloyd at redhat.com:
> On 12/08/2016 08:00 PM, mark.reinhold at oracle.com wrote:
>> ...
>> 
>> Okay, so the obvious thing to do is define `\` as a quotation character
>> for itself, for `:`, and for `@`.  Then you can simply quote/dequote
>> wherever you interface with JPMS.
> 
> That should be fine, I think.
> 
>>> '/' also may be a problem because within our container, we use file
>>> names from the file system as the name of modules that come from the
>>> file system.  This also causes a problem for '\' on Windows.  We could
>>> possibly work out some kind of alternative in this case, with some
>>> creative thinking.
>> 
>> I don't think we need to reserve `/`, as I said to Rémi.
>> 
>> As for `\`, I'm pretty sure that every version of Windows shipped this
>> century will accept `/` in pathnames as an alternative to `\`.
> 
> Yeah, but in any event allowing \ as an escape solves everything, and 
> limiting the number of specials prevents it from becoming too unwieldy, 
> so I'm satisfied with that.

Okay, good.  I'll send a revised proposal for #ModuleNameCharacters
shortly.

- Mark


More information about the jpms-spec-observers mailing list