On 4 Jan 2004 at 2:11, Randy W. Sims wrote:
> BTW, I'd recomment against using F<META.yml> for application specific
> configuration. There is already too much fragmentation in the way
> different tools are generating metadata (see
> <http://www.thepierianspring.org/meta.stats>). It's sole purpose is to
> provide information about a distribution to tools that deal with
> distributions. I believe there is going to be a module soon that will
> provide a standard way to read and write metadata and that looks at and
> validates the metadata, and I think Thomas Klausner is going to use this
> in CPANTS so it may affect the kwalitee of your module.
>
> Oops, dang soapbox slipped up under me. =)
>
> Regards,
> Randy.
>
It ought to be contained in a file in the PAR, so it can be editted and re-zipped
after
pp generation, rather than embedded in the code. How about a new XML file just for
"internal environment variables", that starts with a good string to search for ?
And then a PAR.pm function to retrieve a value from that file, like:
$string = PAR::ENV('PAR_CLEARTEMP');
or a function that sets %ENV from the file:
PAR::import_ENV();
Alan Stewart
