# Perforce Public Depot Jobs # # Job: The job name. 'new' generates a sequenced job number. # Status: Job status; [open/closed/suspended]. Required # Project: The project this job is for [none/cdsp4/jam/p4hl] Optional. # Severity: [A/B/C] (A is highest) Required. # ReportedBy The user who created the job. Can be changed. # ReportedDate: The date the job was created. Automatic. # ModifiedBy: The user who last modified this job. Automatic. # ModifiedDate: The date this job was last modified. Automatic. # OwnedBy: The owner, responsible for doing the job. Optional. # Description: Description of the job. Required. # DevNotes: Developer's comments. Optional. Job: job000014 Status: open Project: jam Severity: C ReportedBy: david_abrahams ReportedDate: 2002/02/25 17:25:46 ModifiedBy: shawn_hladky ModifiedDate: 2008/04/13 13:00:54 Description: Jam reverses slash direction on Windows See: http://maillist.perforce.com/pipermail/jamming/2002-February/001567.html My copy of Jam has the following behavior on Windows: C:\>jam -f- x = foo/bar ; ECHO $(x:G=) ; ^Z foo\bar ^---------------slash direction reversed! DevNotes: (seiwald) Whenever you apply a "file modifier" (PGRDBSM) in a variable expansion, jam assumes it is a file name, tearing it apart and putting it back together. When tearing apart file names on NT, it accepts both \ and /, but when building them it only uses \. The :G (grist) modifier is considered a file modifier. Someday jam will have its own (UNIX) syntax for all file paths, having them turned to local paths only at binding. Someday.