On Thu, Jul 05, 2001 at 11:04:29AM -0700, Hong Zhang wrote:
> I don't think object inheritence has any significant advantage.
> Since it is not widely used and understood, we should not use it
> in Perl, period.
*cough* A little harsh.
> Its functionality can be achieved by many different ways.
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> 'Kay, here's the final version of this.
DS>struct bigint {
DS> void *buffer;
DS> UV length;
DS> IV exponent;
DS> UV flags;
DS>}
DS> =begin question
DS> Should we scrap the buffer pointer and
> What's the problem again?
>
> I mean, really, any OO shop has it's local culture, of what the base
> classes
> are and so forth.
That pretty much sounds like the problem, in a nutshell.
And shop-level is a pretty narrow point of view. What about something that I
d/l from the net, where the cod
I'm writing a little module that implements the $() and @() stuff we've been
talking about (using a source filter), and I just want to make sure I have
it right. This is the SYNOPSIS from my docs; let me know if the behavior
I'm describing is wrong.
sub Foo { '1' }
sub Bar { 1..5
Hong Zhang wrote:
>
> Say if you want Thread can be easily inserted into LinkedList,
> you can write
>
> public Thread extends Object implements Node {
> ...
> }
>
> or
>
> public Thread extends Object, Node {
> ...
> }
>
> and don't bother to implement classic linked list node.
>
> Hong
Here's a feature suggestion for Perl 6.
It would be nice to be able to tell the interpreter to call a user-defined
C function between opcodes. This could make it easier to implement
debuggers, profilers, etc. as well as providing a method of safely using
asynchronous callbacks that certain C lib
Matt Youell wrote:
>
> > > MI thing, but now it's sounding like a constructor bubbling scheme, like
>
>
> Ah, yes. I've had to deal with that problem several times in the past. The
> terminology was new to me, however.
>
> Has there been a proposed solution?
>
> Thanks,
>
> - Matt
What's th
On Thursday 05 July 2001 02:11 pm, Dan Sugalski wrote:
> =begin question
>
> Should we scrap the buffer pointer and just tack the buffer on the end
> of the structure? Saves a level of indirection, but means if we need
> to make the buffer bigger we have to adjust anything pointing to it.
>
> =end
> "UG" == Uri Guttman ([EMAIL PROTECTED]) writes:
UG> it looks pretty powerful which is one reason it may not be good to use
UG> in perl. we don't expect to be doing CORBA level stuff in the core. :)
That wasn't what I had in mind either, but since Perl6 is, as far as I
unde
I don't think object inheritence has any significant advantage.
Since it is not widely used and understood, we should not use it
in Perl, period.
Its functionality can be achieved by many different ways. The
anonymous class is one of them. Personally I prefer using mixin.
The mixin is similar
'Kay, here's the final version of this.
Cut here
=head1 TITLE
Perl's internal data types
=head1 VERSION
1.3
=head2 CURRENT
Maintainer: Dan Sugalski <[EMAIL PROTECTED]>
Class: Internals
PDD Number: 4
Version: 1.3
> "EH" == Espen Harlinn <[EMAIL PROTECTED]> writes:
EH> I think most (all???) of what is needed can be found at:
EH> http://www.cs.wustl.edu/~schmidt/ACE.html
looking it over
EH> I know it's C++, but this framework is well designed - and it is
EH> portable :-) (in other words: it ha
Matt Youell wrote:
> The terminology was new to me, however.
I made it up.
--
John Porter
At 05:29 AM 7/5/2001 -0700, Benjamin Stuhl wrote:
>Thus spake the enlightened Uri Guttman <[EMAIL PROTECTED]>:
> >
> > i am going to make a proposal that we ('we' to be defined
> > later) develop
> > a new common event loop with two major goals in mind:
> >
> > 1. the event loop should be fully
Thus spake the enlightened Uri Guttman <[EMAIL PROTECTED]>:
>
> i am going to make a proposal that we ('we' to be defined
> later) develop
> a new common event loop with two major goals in mind:
>
> 1. the event loop should be fully portable over all
> modern unix OS's
> and the win32 ser
> > What I was suggesting was to consider broadening what the
> > $foo : bar style postfix sub syntax allows/assists bar to do,
> > so that bars can be used to set properties OR do other stuff.
> >
> What's the practical utility of this?
1. Simplification for perl 6 implementation. I would expec
16 matches
Mail list logo
