Re: a modest proposal Re: s/./~/g

2001-04-29 Thread Fred Heutte
I just want to say it seems appropriate that this discussion of how Perl can look like Morse Code is happening in the thread I first started, since I was active in ham radio from 1970-95 (mostly CW, or "Morse Code" to you non-hams). And consider it a blessing that Perl can look like Morse Code, n

Re: Strings vs Numbers (Re: Tying & Overloading)

2001-04-29 Thread David L. Nicol
Bart Lateur wrote: > Yeah. But no cheers then. The problem still remains: you can access a > hash in the normal way in plain code, but inside a sub, you can mainly > only access a passed hash through a reference. > > ... > > Are you going to provide a simpler aliasing mechanism to turn a hash >

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread ashley
> If I work at OReilly, I don't need a Local:: in front of my > OReilly to tell me that it's a local namespace. but you need "OReilly" in front? do you label your clothes "Shirt" and "Pants" as well? might be orthagonal but the top level should serve a useful purpose instead of something along th

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread John Porter
Damian Conway wrote: > If it's a policy, it should go under Policy:: If it's an OReilly site module, it should go under OReilly, eh? What's general and what's specific is entirely a matter of perspective, since "OReilly" and "Policy" are entirely orthogonal concepts. > Surely you wouldn't condo

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Simon Cozens
On Sun, Apr 29, 2001 at 05:06:03PM -0400, John Porter wrote: > OReilly::Policy is (or might be) still general before > specific. OReilly::* might be a whole family of site- > specific modules. Policy::* is *guaranteed* to be a large family of site-specific modules, hopefully even larger than th

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Damian Conway
> > You Americans and your non-ISO penchant for putting the specific before > > the general. Surely that should be: > > > > use Policy::O::Reilly; > > I knew someone would argue that, but I didn't think it would > be someone as illustrious as Damian. Illustrious???

Re: a modest proposal Re: s/./~/g

2001-04-29 Thread John Porter
Larry Wall wrote: > Now we just need to make "... ___ ..." mean something exceptional. Ref: http:[EMAIL PROTECTED]/msg02873.html ) -- John Porter

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread John Porter
Damian Conway wrote: > You Americans and your non-ISO penchant for putting the specific before > the general. Surely that should be: > > use Policy::O::Reilly; I knew someone would argue that, but I didn't think it would be someone as illustrious as Damian. Do you think Larry doesn't kn

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Ask Bjoern Hansen
On Sun, 29 Apr 2001, Michael G Schwern wrote: > Unfortunately, the perl6-language archive doesn't seem to go back far > enough to cover the .perlrc discussion. Is the old archive still > around? don't know which archive you are talking about, but http://archive.develooper.com/perl6-language%40p

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Michael G Schwern
On Sun, Apr 29, 2001 at 12:20:42PM -0700, Ask Bjoern Hansen wrote: > don't know which archive you are talking about, but > http://archive.develooper.com/perl6-language%40perl.org/ should have > all mails sent to perl6-language from it's start to a few days ago > when I moved stuff around. I think

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Michael G Schwern
On Sun, Apr 29, 2001 at 12:49:28PM -0400, Dan Sugalski wrote: > At 05:37 PM 4/29/2001 +0100, Michael G Schwern wrote: > >By "optional" I take it you mean an admin can choose to define their > >own site policy or not? > > No. Optional in that you have to do a "use SomePolicyThingWeHaventDecided;"

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Dan Sugalski
At 05:37 PM 4/29/2001 +0100, Michael G Schwern wrote: >On Sun, Apr 29, 2001 at 11:44:24AM -0400, Dan Sugalski wrote: > > At 04:30 PM 4/29/2001 +0100, Michael G Schwern wrote: > > >To use a Perl 5 example, consider the simple setting of "use strict" > > >as a general site policy. Basicaly, most of

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Michael G Schwern
On Sun, Apr 29, 2001 at 11:44:24AM -0400, Dan Sugalski wrote: > At 04:30 PM 4/29/2001 +0100, Michael G Schwern wrote: > >To use a Perl 5 example, consider the simple setting of "use strict" > >as a general site policy. Basicaly, most of the Perl code in your > >/usr/bin will explode when you try

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Dan Sugalski
At 04:30 PM 4/29/2001 +0100, Michael G Schwern wrote: >On Sat, Apr 28, 2001 at 02:44:17PM -0400, Dan Sugalski wrote: > > Well, I was thinking that generally the site policy would be expressed > in a > > single file > >This smells strangely familiar. Alot like the .perlrc discussion that >was had

Re: a modest proposal Re: s/./~/g

2001-04-29 Thread Michael G Schwern
On Sat, Apr 28, 2001 at 10:39:01AM -0700, Larry Wall wrote: > Now we just need to make "... ___ ..." mean something exceptional. ___ ... ___ is valid. :) -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalite

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Michael G Schwern
On Sat, Apr 28, 2001 at 02:44:17PM -0400, Dan Sugalski wrote: > Well, I was thinking that generally the site policy would be expressed in a > single file This smells strangely familiar. Alot like the .perlrc discussion that was had back many moons ago. The havoc a general syntax-altering polic

Re: Flexible parsing (was Tying & Overloading)

2001-04-29 Thread Dan Sugalski
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