Re: Flexible parsing (was Tying Overloading)
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. You Americans and your non-ISO penchant for putting the specific before the general. Surely that should be: use Policy::O::Reilly; # really gonna miss that ' package separator ;-) or use Policy::Mongolian::Navy::Office::Procurement; Next you'll be putting the month and day before the year in dates! Damian
Re: a modest proposal Re: s/./~/g
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
Re: Flexible parsing (was Tying Overloading)
[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: : : use Policy::O::Reilly;# really gonna miss that ' package separator :;-) : : or : : use Policy::Mongolian::Navy::Office::Procurement; Well, I did say more in order. I didn't say how much more. : Next you'll be putting the month and day before the year in dates! No, that isn't next, that was previous. Perhaps, being hemispherically challenged, you're looking at it upside down. (-:, er, that is, :-) Larry
Re: Flexible parsing (was Tying Overloading)
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 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. Well, I was thinking that generally the site policy would be expressed in a single file, and might look something like: Perl: set parser Perl (global); set warnings on (global, fixed); set strict on (global, fixed); Python: set parser Python (global); EasyPerl: set parser Perl (global); set warnings on (global); set strict off; Basically a simple config file that can be protected as the site administrator might see fit, with a simple syntax rather than perl code. (Though if the perl code's straightforward for this stuff, then it doesn't much matter either way) I hadn't really considered having a separate module for each type of site policy decision. Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: a modest proposal Re: s/./~/g
: 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---cut-- use Morse; .--.-..--..---.-.--..--.-..--..---.-.--. .-.----..-..---.-..-.--..---.--. ..-.---..-...-...-..--..-.-.-.--.-.. ..-.-.--.-..--..-.-...---.-..---.--. .-...-..--.---...-.-
Re: Flexible parsing (was Tying Overloading)
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
