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}.
Yes without a doubt there are examples of those already. The algorithm
that I currently use to uncover suchlike is:
$ search config.h "$"
Although I think that the automatization that Dan has hinted at may do
something considerably more perlian :-). FWIW I do not think that we have
all of the config $variables set in a patched RC1_1 as yet and we will
need to modify the algortihm that I sent in to "set" {xs|pm}_apiversion.
Although it may prove worhtwhile to wait for the Unix version to hint at
what to do there (uncertainty has to do with the difference in string
formatting in going from "5.005" (or "5_005" on vms/dos) to "5_6_0" and such).
I think that the last integer ought to be formatted %03d for certain values
different from zero but I could still be wrong about that(?).
Peter Prymmer
