Re: RFC 260 (v1) More modules

2000-09-21 Thread Bart Lateur
On 19 Sep 2000 19:41:20 -, Perl6 RFC Librarian wrote: >Perl should come distributed with more modules. I know of people/sites where installing the whole lot of Perl just to run a tiny script, is not acceptable as an option. Not everyone is a developer. -- Bart.

Re: RFC 228 (v1) Add memoize into the standard library

2000-09-15 Thread Bart Lateur
On Fri, 15 Sep 2000 08:28:30 -0700 (PDT), Dave Storrs wrote: > Personally, I like the way it works at the moment; all the subs >that you want to memoize are up at the top, where they are easy to see. You have a point. What I don't like is how the basic module syntax pretty much requires t

Re: RFC 228 (v1) Add memoize into the standard library

2000-09-15 Thread Bart Lateur
On 15 Sep 2000 02:09:23 -, Perl6 RFC Librarian wrote: >A version of Memoize.pm should be added into the Perl6 standard >library, and it should be added as a pragmatic module (i.e. memoize.pm). Is that it? I would rather have a flag when generating the sub, er, what's that syntax again, ":so

Re: How to implement both object->method and module::function interface?

2000-08-09 Thread Bart Lateur
On Wed, 9 Aug 2000 14:26:25 +0100, Graham Barr wrote: >That is being considered. IF that does become part of the language I could >see subs do something like > > if (defined $SELF) { >called as a method > } > else { >called as a sub > } That was my idea. The current unfixable bug I

Re: How to implement both object->method and module::function interface?

2000-08-09 Thread Bart Lateur
On Wed, 09 Aug 2000 13:58:34 +0100, Hildo Biersma wrote: >Yikes. Class method calls should perform inheritance, subroutine calls >should not. I agree with that. >Altering the language to make the two look the same is a bad >idea, because it breaks, fatally, as soon as the class supports more >

Re: How to implement both object->method and module::function interface?

2000-08-09 Thread Bart Lateur
On Wed, 09 Aug 2000 11:41:20 +0100, Hildo Biersma wrote: >Could we agree on the idea that CGI.pm should be split up? No. I could agree that CGI->somemethod(@args); would do exactly the same as CGI::somemethod(@args); i.e. no difference between function calls and class methods

Re: How to implement both object->method and module::function interfa ce?

2000-08-08 Thread Bart Lateur
On Tue, 8 Aug 2000 14:22:20 -0500 , Garrett Goebel wrote: >What's the conventional wisdom on creating a module that supports both an OO >and non-OO interface? Are there any CORE or CPAN modules to serve as a >textbook, or is the anwser "Don't do that"? > >I've got some code that checks the first

Re: Define consistent and standard

2000-08-07 Thread Bart Lateur
On Sun, 6 Aug 2000 01:13:22 +1000, [EMAIL PROTECTED] wrote: >* Variables are things are nouns. Give them noun names. > $name, $total, $input >* Plural variables should have plural names > @employees, @items, %contact_details Hmmm... >* Hash names should be written so that looking up