At 04:16 PM 3/14/00 -0500, Charles Bailey wrote:
> > '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}.
Yup. And, for those things that are undef at least, we may need to define
them in the future. I'd really like to have subconfigure probe for
*everything*, though that's gonna hurt bad on some Vaxen.
We can, and probably should, combine some of the tests--no reason we can't
probe for sizes of things in one go, rather than one per thingie.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
