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. Larry
- Re: Flexible parsing (was Tying & Overl... Jarkko Hietaniemi
- Re: Flexible parsing (was Tying & O... Nicholas Clark
- Re: Flexible parsing (was Tying & Overloading) Eric Roode
- Re: Flexible parsing (was Tying & Overloading) Dan Sugalski
- Re: Flexible parsing (was Tying & Overloadi... Larry Wall
- Re: Flexible parsing (was Tying & Overl... John Porter
- Re: Flexible parsing (was Tying & O... Larry Wall
- Re: Flexible parsing (was Tying & Overl... Dan Sugalski
- Re: Flexible parsing (was Tying & O... Larry Wall
- Re: Flexible parsing (was Tying &a... Dan Sugalski
- Re: Flexible parsing (was Tyin... Larry Wall
- Re: Flexible parsing (was Tyin... Dan Sugalski
- Re: Flexible parsing (was Tyin... Tim Bunce
- Re: Flexible parsing (was Tyin... Michael G Schwern
- Re: Flexible parsing (was Tyin... Dan Sugalski
- Re: Flexible parsing (was Tyin... Michael G Schwern
- Re: Flexible parsing (was Tyin... Dan Sugalski
- Re: Flexible parsing (was Tyin... Michael G Schwern
- Re: Flexible parsing (was Tyin... Ask Bjoern Hansen
- Re: Flexible parsing (was Tyin... Michael G Schwern
- Re: Flexible parsing (was Tying & Overloading) Damian Conway