Re: Added get-env-var to asdf

Rahul Jain wrote:
> Robert Goldman <[email protected]> writes:
> 
>> I understand that ASDF is not a portability library, but it seems like 
>> environment variables are a reasonable way to configure ASDF systems, 
>> permitting contextual tailoring that extends the capability of *features*.
> 
> Why doesn't *features* suffice? What are you (all) doing that relies on
> invoking a lisp directly from the command line without the opportunity
> to frob *features* first?
> 

Features are boolean kinds of things.  What about the case where you 
want to specify, for example, a directory location?  This seems like a 
not-uncommon case.

On the other hand, now that I think about it more, I thought that Gary 
had already added the ability to read configuration files.  If that's 
true, then my argument for the use of environment variables collapses.

As far as Dan's argument about the windows registry, I don't think 
that's valid, because environment variables are a lowest common 
denominator, available in Windows and the Unices, something which cannot 
be said of registry access, or some KDE thing, for example.

On the other other hand, as I said above, Gary's previous inclusion of 
config files probably takes the wind out of the sails of my argument.

If there are config files, then I don't see the need for environment 
variables (but I haven't thought deeply about the issue).

Best,
Robert

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV