> I think we have to be careful here. We should ask people to name site
> policy files after their site, and not use a generic name like
> "site_policy", since we'd be likely to end up with 20 different
> "standard" site_policy files wandering around the net. So something
> like
Simon Cozens writes:
: Hey, that would make "_ _ __" legal Perl code. Abigail, Abigail!
Now we just need to make "... ___ ..." mean something exceptional.
: (I still prefer ~, but acknowledge that this is just bikeshed painting.)
Bikesheds need to be painted occasionally.
Larry
[EMAIL PROTECTED] writes:
:> use OReilly::Policy;
:>
:> or
:>
:> use Mongolian::Navy::ProcurementOffice::Policy;
:>
:> might be more in order.
:
: You Americans and your non-ISO penchant for putting the specific before
: the general. Surely that should be:
:
At 01:51 PM 4/27/2001 -0700, Larry Wall wrote:
>Dan Sugalski writes:
>: Besides, having the site administrator forbid the installation of parser
>: tweaks might not be what is wanted. If we get PPython in there, a site may
>: well have a Python.pm module handy, and source might start:
>:
>:use
> : Hey, that would make "_ _ __" legal Perl code. Abigail, Abigail!
>
> Now we just need to make "... ___ ..." mean something exceptional.
Just download the Bleach.pm module from the CPAN.
It includes Morse.pm.
Damian
---cut---cut---cut---cut---
Dan Sugalski writes:
: I hadn't really considered having a separate module for each type of site
: policy decision.
Er, neither had I. Each site only has one policy file. I just want it
named after the actual site, not some generic name like "Policy". I
think policy files are inherently non-p
