Please look at Class::Object before responding. URL below.
On Fri, Jun 29, 2001 at 06:36:31PM -0400, John Porter wrote:
> [EMAIL PROTECTED] wrote:
> > "Any sufficiently encapsulated hack is no longer a hack."
>
> Who said that? I think it's wrong.
Me.
> Any sufficiently encapsulated hack i
[EMAIL PROTECTED] wrote:
> "Any sufficiently encapsulated hack is no longer a hack."
Who said that? I think it's wrong.
Any sufficiently encapsulated hack is no longer a *naked* hack. So what.
> You shouldn't be relying on an object's reference. ref $obj eq
> 'Some::Class' wrecks subclassin
On Fri, Jun 29, 2001 at 12:59:32PM -0800, Michael Fowler wrote:
> If you're relying on an overload isa() method to determine if something
> belongs to a given class you're going to run into problems.
There's no overloads, I never touched isa()! It all just works!
LOOK AT CLASS::OBJECT!
http://w
On Fri, Jun 29, 2001 at 04:42:57PM -0400, [EMAIL PROTECTED] wrote:
> > It's also not without its faults. Having every instance of a
> > class have different values of ref() could be obnoxious, for
> > example.
>
> Why? You shouldn't be relying on an object's reference. ref $obj eq
> 'Some::Cla
On Fri, Jun 29, 2001 at 04:22:45PM +0200, Marcel Grunauer wrote:
> Additions and suggestion for the page are welcome, please send them to
> [EMAIL PROTECTED]
Well, its not yet know if any of this will make it into Perl 6, but
they're based on RFCs and perl6 discussions...
UNIVERSAL::exports
CLAS
On Fri, Jun 29, 2001 at 09:50:55AM -0400, Dan Sugalski wrote:
> At 10:32 PM 6/28/2001 -0400, Michael G Schwern wrote:
> >The rule of thumb has always been if you can do it in a module, don't
> >put it in the core. Well, we can do it in a module. Work on the
> >module, don't complicate the core.
On Fri, Jun 29, 2001 at 08:59:59AM -0400, John Porter wrote:
> Michael G Schwern wrote:
> > Second, and perhaps more importantly, we can do this perfectly well
> > with a module. No hacks, no tricks, no filters.
> > Class::Object uses the mini-class technique (ie. auto-generated
> > classes
>
>
On Sunday, 10 June 2001, Peter Scott <[EMAIL PROTECTED]> wrote:
> He's right. I do a lot of DBI stuff with Oracle, and every so often
> I have a hankering for some kind of structured tied variable that
> would look like my database. Then I wake up and realize that modeling
> of a single table does
At 05:22 PM 6/28/2001 -0500, David L. Nicol wrote:
>Garrett Goebel wrote:
>
> > > So every class has a vtable, which is a copy of its parents except for
> > > what is overridden within it, and a instance that wishes to
> > > deviate could make a local copy of its vtable and twiddle it.
>
> > Why n
At 07:53 AM 6/29/2001 -0600, Nathan Torkington wrote:
>Dan Sugalski writes:
> > Doing it properly in a module is significantly more of a pain than
> doing it
> > in the core. Faking it with a module means a fair amount of (reasonably
> > slow) perl code, doing it in the core requires a few extra
At 06:07 PM 6/28/2001 -0700, Brent Dax wrote:
>I'd think that @ISA would be copied to .ISA on object instantiation, and
>after that the two wouldn't have anything to do with each other. We could
>set up one of those cool copy-on-write locks everyone's been talking about
>to save memory too.
Yep,
I've done a web page with information and links to Perl 5 modules
that may be of interest to this list. Some of them are
proof-of-concepts of Perl 6 features that the respective authors
have implemented to show how things *might* work in Perl 6.
It's at http://www.codewerk.com/perl6/ .
(If you'
Dan Sugalski writes:
> Doing it properly in a module is significantly more of a pain than doing it
> in the core. Faking it with a module means a fair amount of (reasonably
> slow) perl code, doing it in the core requires a few extra lines of C code
> in the method dispatch opcode function.
Wo
At 10:32 PM 6/28/2001 -0400, Michael G Schwern wrote:
>The rule of thumb has always been if you can do it in a module, don't
>put it in the core. Well, we can do it in a module. Work on the
>module, don't complicate the core.
Doing it properly in a module is significantly more of a pain than do
Michael G Schwern wrote:
> Second, and perhaps more importantly, we can do this perfectly well
> with a module. No hacks, no tricks, no filters.
> Class::Object uses the mini-class technique (ie. auto-generated
> classes
Sorry, that sounds like a hack/trick if ever there was one.
I would sure h
15 matches
Mail list logo
