At 02:28 PM 3/14/00 -0800, [EMAIL PROTECTED] wrote:
>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 :-).
Not too much so. If an unknown token's surrounded by double-quotes it'll
get replaced with the empty string, and unknown tokens that have a # before
them'll get replaced with undef. Anything fancier's just too darned much
work in C. :)
Dan
----------------------------------------------------------------------------
Dan Sugalski General and VMS-specific perl training
[EMAIL PROTECTED]
Mail me for more details
