Front page | perl.perl5.porters |
Postings from October 1999
On Fri, Oct 22, 1999 at 10:46:26AM -0700, Chip Salzenberg wrote:
>According to Ed Peschko:
>> On Thu, Oct 21, 1999 at 06:26:12PM -0700, Chip Salzenberg wrote:
>> >According to Ed Peschko:
>> >> Ok, then I guess the best way around this (assuming that you want to enforce
>> >> control on something like 'use strict') is to have the option to put PERL5OPT
>> >> in the executable, and then have a 'Common' module which contains horrifically
>> >> obscure code to insert the 'use' statements into each and every right
>> >> namespace.
>> >
>> >"Right" namespace? How do you know which ones are "right", even in theory?
>>
>> By checking %INC, and discarding all third-party modules, and concentrating
>> on ones developed 'in house'.
>
>Sounds like you need an in-house module to know what's in-house.
yeah, that's what I was thinking. Although I could see abstracting it -
something like:
use Config;
use AutoExport qw
[
ignore => $Config{installprefix},
defaulttext => 'use ...; use ....; use ....; use ....;'
];
This is getting pretty whacked out though. I think a hook compiling PERL5OPT
would be enough for what I need.
Ed
Thread Previous
|
Thread Next