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 site_policy qw(Python); : : for modules that were all-Python, or : : use site_policy qw(Perl); : : for ones that were all-perl. The site-policy file would, amongst other : things, perhaps lock down the parser so you couldn't switch languages in : mid-file. 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 use OReilly::Policy; or use Mongolian::Navy::ProcurementOffice::Policy; might be more in order. Larry
- Re: Flexible parsing (was Tying & Overloading) Jarkko Hietaniemi
- Re: Flexible parsing (was Tying & Overloadi... Simon Cozens
- 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