Re: RFC 125 (v2) Components in the Perl Core Should Have Well-Defined APIs and Behavior

2000-10-05 Thread Dan Sugalski
At 06:19 PM 10/5/00 +0200, Philip Newton wrote: >On 2 Oct 2000, at 16:14, Dan Sugalski wrote: > > > At 04:34 PM 9/29/00 -0400, John Porter wrote: > > >Dan Sugalski wrote: > > > > > > > > I've no experience with UML, though. Got a pointer to a quick overview? > > > > > >Without a doubt, "UML Distil

Re: RFC 125 (v2) Components in the Perl Core Should Have Well-Defined APIs and Behavior

2000-10-05 Thread Dan Sugalski
At 07:51 PM 10/5/00 +0200, Philip Newton wrote: >On 5 Oct 2000, at 13:44, Dan Sugalski wrote: > > > At 06:19 PM 10/5/00 +0200, Philip Newton wrote: > > >On 2 Oct 2000, at 16:14, Dan Sugalski wrote: > > > > > > > I'll have to go pick that up on Thursday and add it to the Darned > Big Pile > > > >

Re: RFC 125 (v2) Components in the Perl Core Should Have Well-Defined APIs and Behavior

2000-10-05 Thread Philip Newton
On 2 Oct 2000, at 16:14, Dan Sugalski wrote: > At 04:34 PM 9/29/00 -0400, John Porter wrote: > >Dan Sugalski wrote: > > > > > > I've no experience with UML, though. Got a pointer to a quick overview? > > > >Without a doubt, "UML Distilled" is the bible of the genre. > > I'll have to go pick that

Re: RFC 125 (v2) Components in the Perl Core Should Have Well-Defined APIs and Behavior

2000-10-05 Thread Philip Newton
On 5 Oct 2000, at 13:44, Dan Sugalski wrote: > At 06:19 PM 10/5/00 +0200, Philip Newton wrote: > >On 2 Oct 2000, at 16:14, Dan Sugalski wrote: > > > > > I'll have to go pick that up on Thursday and add it to the Darned Big Pile > > > of books I need to read. > > > >Funny how everyone seems to hav

Re: RFC 326 (v1) Symbols, symbols everywhere

2000-10-05 Thread Chaim Frenkel
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: DS> For the internals, though... DS> This would be very useful, and it's a feature I'd really like to implement. DS> Basically you're asking for pre-computed, indirect, shared hash keys. This DS> sounds like a Good Plan to me. Why precomp

Re: RFC 361 (v1) Simplifying split()

2000-10-05 Thread Chaim Frenkel
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: PRL> =item 2. Empty trailing fields are currently suppressed (although a PRL> -1 as the third argument disables this). I suggest that empty trailing PRL> fields be retained by default. Extremely useful, I rely on this. It makes non-