Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-31 Thread chromatic
On Wednesday 30 August 2006 19:14, Luke Palmer wrote: > The problem with PHP is not that it has > too much functionality, but that it is organized extremely poorly. That's really my point. I'm all for adding necessary features to Parrot where they're appropriate, but not in such a way that they

Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-30 Thread peter baylies
On 8/31/06, Mark J. Reed <[EMAIL PROTECTED]> wrote: On 8/30/06, Luke Palmer <[EMAIL PROTECTED]> wrote: > > The problem with PHP is not that it has > too much functionality, but that it is organized extremely poorly. Amen. PHP is the poster child for namespace pollution. And PHP5 actually has

Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-30 Thread Mark J. Reed
On 8/30/06, Luke Palmer <[EMAIL PROTECTED]> wrote: The problem with PHP is not that it has too much functionality, but that it is organized extremely poorly. Amen. PHP is the poster child for namespace pollution. And PHP5 actually has the tools to stop the madness; it's just a question of

Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-30 Thread Luke Palmer
On 8/30/06, chromatic <[EMAIL PROTECTED]> wrote: On Wednesday 30 August 2006 04:12, Watson Ladd wrote: > Seriously, what's so bad about adding functionality into > a language? I once saw an overfilled waterbed that was almost as tall as I am. I would have called it PHP, but it didn't explode a

Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-30 Thread chromatic
On Wednesday 30 August 2006 04:12, Watson Ladd wrote: > Seriously, what's so bad about adding functionality into > a language? I once saw an overfilled waterbed that was almost as tall as I am. I would have called it PHP, but it didn't explode and throw cold water all over the house. -- c

Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-30 Thread Watson Ladd
Matt Diephouse wrote: Joshua Juran <[EMAIL PROTECTED]> wrote: On Aug 28, 2006, at 12:18 PM, Matt Diephouse wrote: > I would like to add some sort methods as well: quicksort(), > mergesort(), etc. But as methods, there is potential for these to end > up in a user-visible space. > > Say for examp

Re: Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-29 Thread Matt Diephouse
Joshua Juran <[EMAIL PROTECTED]> wrote: On Aug 28, 2006, at 12:18 PM, Matt Diephouse wrote: > I would like to add some sort methods as well: quicksort(), > mergesort(), etc. But as methods, there is potential for these to end > up in a user-visible space. > > Say for example, that I add a merges

Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-29 Thread Joshua Juran
On Aug 28, 2006, at 12:18 PM, Matt Diephouse wrote: I would like to add some sort methods as well: quicksort(), mergesort(), etc. But as methods, there is potential for these to end up in a user-visible space. Say for example, that I add a mergesort method to AbstractPMCArray. Ruby's array clas

PMC Methods, Inheritance, and User-visible Classes

2006-08-28 Thread Matt Diephouse
I'm going to start working on an AbstractPMCArray PMC class that can provide some default array vtable functions for other PMCs to inherit. This will give array classes some functionality for free. AbstractPMCArray will implement splice, for example, which can be implemented using an array's exter