[jamming] Path specification (was: Majam - keeping jamup-to-date)

[Johan Nilsson]

> -----Original Message-----
> From: jamming-bounces at perforce.com 
> [mailto:jamming-bounces at perforce.com] On Behalf Of Kai Backman
> Sent: den 11 augusti 2006 15:52
> To: Alen Ladavac
> Cc: Tim Sneddon; jamming at perforce.com
> Subject: Re: [jamming] Path specification (was: Majam - 
> keeping jamup-to-date)
> 
>  Here is a two part solution:
> 
> 1. Define a portable path format for use in jam, jambase and 
> jamfile's on all platforms
> 
> 2. Add two modifiers, similar to what Alen has adopted, one 
> for converting native into portable ':~' and one to convert 
> from portable to native ':/'

I'd prefer something like the T/F modifiers suggested by David Turner
(or why not N(ative)/P(ortable - if they aren't already used).

> 
> 
>  Based on my quick reading of the OpenVMS links provided by 
> John and Tim a portable path could be defined as follows:
> 
> Absolute path:
> "drive:/subpath1/subpath2/file.ext;v"
>  where drive: and ;v optional, leading / mandatory
> 
> Relative path:
> "../subpath/file.ext;v"
>  where ;v optional, leading non-/ mandatory

Well, for portable paths, I'd prefer a leading / for absolute paths and
to get rid of the version altogether, i.e.:

Absolute path:
"/drive:/subpath1/subpath2/file.ext"
 
Relative path:
"subpath/file.ext"

Globbing should always return portable paths on all platforms (version
stripped under VMS).

/ Johan