[jamming] Majam - keeping jam up-to-date

Johan Nilsson johan.nilsson at esrange.ssc.se
Thu Aug 10 00:34:22 PDT 2006


 

> -----Original Message-----
> From: jamming-bounces at perforce.com 
> [mailto:jamming-bounces at perforce.com] On Behalf Of Alen Ladavac
> Sent: den 10 augusti 2006 08:51
> To: jamming at perforce.com
> Subject: Re: [jamming] Majam - keeping jam up-to-date
> 
> > I see the `needed _host_` problem a little different. If jam can be 
> > ported on a platform, port it. I dont see how that would greatly 
> > influence other files than the builtin-Jambase, which has 
> around 1200 
> > lines.
> 
> The biggest problem I see is for example old MacOS using ":" 
> both as SLASH and as DOT, and "::" as a DOTDOT. Also, VMS 
> using "." as SLASH and "[]"/"[-]" as DOT/DOTDOT. The 
> potential problem here is that I see a lot of mumbo-jumbo 
> going on in path parsing and in the default Jambase in order 
> to work with these strange setups. In my modifications, I 
> simply allowed the paths to be specified directly with "/", 
> and only eventually is that converted to "\" on NT when 
> needed. I have completely removed the notions of SLASH, DOT 
> and DOTDOT, what simplified the scripts a lot, and simplified 
> the code itself somewhat.
> 
> Now, I don't have any experience in those systems whatsoever, 
> so I don't claim I know whether it might still be possible to 
> use the "/"-only paths and convert when needed. But if it is 
> not, the first thing I'd do would be to drop support for 
> those OSs. I simply don't expect to need it ever. Perhaps I'm 
> a bit selfish, but I like to simplify things for me. :)

Well, I need VMS support for a couple of more years, so don't drop it
;-)

/ Johan



More information about the jamming mailing list