19 messages in com.perforce.jamming[jamming] RFC: On the future of Jam, ...
FromSent OnAttachments
David Turner29 Jun 2001 01:48 
Werner LEMBERG29 Jun 2001 03:00 
Robert Cowham29 Jun 2001 03:57 
David Turner29 Jun 2001 04:07 
David Turner29 Jun 2001 05:29 
Arnt Gulbrandsen29 Jun 2001 06:42 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)29 Jun 2001 06:49 
Jos Backus29 Jun 2001 09:30 
Beman Dawes29 Jun 2001 10:29 
David Turner29 Jun 2001 11:07 
Jos Backus29 Jun 2001 11:23 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)29 Jun 2001 12:45 
Werner LEMBERG30 Jun 2001 23:36 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)01 Jul 2001 05:53 
Roger Lipscombe02 Jul 2001 03:15 
David Turner02 Jul 2001 06:40 
David Turner02 Jul 2001 06:54 
Jos Backus02 Jul 2001 11:07 
Paul Moore02 Jul 2001 12:37 
Subject:[jamming] RFC: On the future of Jam, "FT Jam" and Boost
From:Jos Backus (jo@cncdsl.com)
Date:07/02/2001 11:07:26 AM
List:com.perforce.jamming

Hi David,

On Mon, Jul 02, 2001 at 03:40:39PM +0200, David Turner wrote:

into the binary, they live in /usr/share/mk/*.mk.

Yes, but that scheme is not going to translate well on Windows, OS/2, and a few other platforms supported by Jam, where hard-coded paths aren't exactly the default..

True. One could use registry settings or OS2.INI entries in those environments.

I think that both approachs have their merits. After all, we can easily choose to use the "/usr/share/jam/..." thing on Unix-style systems, and the single-exe one on other ones.

As long as the tool is easily extensible by users, either though environment variables, .jamrc files, command line flags, etc.. it really doesn't make much of a difference where the defaults are stored :-)

Absolutely!

Cheers,

-- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jo@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer;