At 03:44 PM 4/28/2001 -0700, Larry Wall wrote:
>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-portable, so they should be named
>that way.
Ah. I was thinking that site_policy.pm (or whatever extension perl 6
modules get) would be the code we provide that handles all the policy
setting, with it reading off of some config file in some standardized spot.
(I can easily see a site having multiple policies, FWIW) From an admin
position, I'd much rather have perl use one single file in a known location
regardless of where I was, but I don't really care all that much.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloading) Larry Wall
- Re: Flexible parsing (was Tying & Overloading) John Porter
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloading) Larry Wall
- Re: Flexible parsing (was Tying & Overloading) Damian Conway
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloading) Larry Wall
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloading) Tim Bunce
- Re: Flexible parsing (was Tying & Overloading) Michael G Schwern
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloading) Michael G Schwern
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloading) Michael G Schwern
- Re: Flexible parsing (was Tying & Overloading) Ask Bjoern Hansen
- Re: Flexible parsing (was Tying & Overloading) Michael G Schwern
- Re: Flexible parsing (was Tying & Overloading) John Porter
- Re: Flexible parsing (was Tying & Overloading) Simon Cozens
