On Sat, Apr 28, 2001 at 03:44:25PM -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. FYI, the module list has said this for several years: : If developing modules for private internal or project specific use, : that will never be released to the public, then you should ensure that : their names will not clash with any future public module. You can do : this either by using the reserved Local::* category or by using an : underscore in the top level name like Foo_Corp::*. Tim.
- 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
- Re: Flexible parsing (was Tying & Overloading) Damian Conway