Walter Bright wrote:
> No paths at all will be allowed in the import string. They'll have to be supplied via the -Jpath command line switch. It's probably more conservative than necessary, but:
> 
> 1) introducing host system dependent path separators makes the source code non-portable

Don't all systems in any amount of use these days accept '/'? (Yes, that includes Windows)

> 2) it gives the 'buildmaster' an easy way to find out and control what files are imported
> 
> 3) I think it's best to err on the side of conservatism here

Well, at least it won't break any code if you later decide to allow paths...

Frits van Bommel wrote:
> Walter Bright wrote:
>> No paths at all will be allowed in the import string. They'll have to be supplied via the -Jpath command line switch. It's probably more conservative than necessary, but:
>>
>> 1) introducing host system dependent path separators makes the source code non-portable
> 
> Don't all systems in any amount of use these days accept '/'? (Yes, that includes Windows)

Sort of.  The windows command shell is supposed to, but it's not usable.  For example "cd /" doesn't change to the root directory and "more /autoexec.bat" won't dump the contents of that file to the screen.  But we're talking about path separators in source code anyway, and '/' has been accepted by compilers for as long as I can remember.


Sean