Re: Re: Explicit import of environment variables

From: Johan Nilsson (johan.nilsson_at_[hidden])
Date: 2004-10-21 02:59:41

"Victor A. Wagner Jr." <vawjr_at_[hidden]> wrote in message
news:6.1.2.0.2.20041020094233.07a3ff68_at_mail.rudbek.com...
>

[snip]

> > > Would it be possible to add an explicit native rule to do this,
asimilar
> > > to the w32_getreg functionality? Perhaps vms_import <list of
environment
> > > var names/logical names>:
> > >
> > > var_values_list = [ vms_import "X" "Y" "Z" ] ;
>
> change vms_import to explicit_import
> I believe everyone's objections will go away

Good suggestion. That would be fine with me, at least for the time being.

>
> -or-
>
> can't you do X = $X (that's old make syntax, but you get the drift)
> if not, why not?

This is my understanding (someone correct me if I'm wrong):

The environment is imported at (b)jam invocation by using either the
(non-portable?) "extern char** environ" or the envp arg to main. The "X =
$X" (X = $(X) in jam) would only look for X in the already imported (and the
internal) variables, not reaching out to the current environment using e.g.
getenv. And as enumeration of the "environment" is not supported under
OpenVMS ... well ...

I can of course do:

bjam "-sX=x_val" "-sY=y_val"

but who would like to do that on a regular basis?

// Johan