> 'define' on VMS and they ought not even incur the expense of any symbol d_foo
> or perl_d_foo. Hence there are at least three classes of conf variables: those
> that are completely ignorable on VMS and do not even need to be in our
> config.sh, those that take certain fixed values such as '' or 'undef', etc.;
We need to be a bit careful here, because config.sh gives rise to Config.pm,
so we may need to include vars which aren't directly meaningful under VMS
in order to avoid a failure when some lib module looks up $Config{foo}.
Regards,
Charles Bailey [EMAIL PROTECTED]
