On Sun, Oct 28, 2001 at 08:36:31PM -0500, John Siracusa wrote:
> On 10/28/01 7:57 PM, Damian Conway wrote:
> > method foo is lvalue {
> > return $foo;
>
> Any word on automagical creation of these suckers? No, not as a module, but
> built-in.
They're called "
On 10/28/01 7:57 PM, Damian Conway wrote:
> method foo is lvalue {
> return $foo;
Any word on automagical creation of these suckers? No, not as a module, but
built-in. I don't think it's too crazy to build *some* sort of sensible
attribute accessor auto-creat
On 10/28/01 7:03 PM, Damian Conway wrote:
> Brent asked:
>> I assume we're going to recycle 'my' and 'our' to be 'instance' and
>> 'class'--is that correct?
>
> That's what I'm proposing.
So should I start practicing my typos for "instance" now? Insatance
instancae instance. Mmmm... ;P
> I fa
Aaron wrote:
> Several questions come up.
>
>* If $.foo is "like" the Perl5 $self->{foo},
Except (as I'm sure you know) that Perl 6 class instantiations aren't
hashes, and their attributes aren't hash entries.
> how do I do the Perl5 $self->foo?
.foo()
>* Is "fo
Damian Conway <[EMAIL PROTECTED]> writes:
> Brent told us:
>> All these Star Trek references are threatening to make my warp core
>> breach... :^)
>
> Too much information.
Look, I'm sorry, okay? I only finished up the article with a Trek
reference because, whilst I could see Larry as G
Brent asked:
> # Well, I'm not a Damian, but I play one on perl6-language. ;-)
>
> Well, then, where's a *real* Damian? :^)
The Real Damian is the Damian inside each of us.
You need to get in touch with your *own* inner Damian.
;-)
> I assume we're going to recycle 'my' and '
On Sun, Oct 28, 2001 at 01:26:28PM -0500, Sam Tregar wrote:
> Maybe I'm anal retentive, but I don't know if I'm ready to start writing
> methods I can't test!
You prefer to write tests for things that don't exist? :) Ah well, have
it your own way. (That's to say, yes, I'd love to see some tests f
Hi all,
I made some little changes to pbc2c.pl to make it work with all
(working) examples.
I'm sorry that it throws some nasty warnings, maybe it's possible
to remove them using opcode_t * instead of int.
Opinions more than welcome.
Brent Dax:
# 1. No if(s|sc, i|ic)
# We're treating strings as second-class citizens here. Why
# shouldn't you
# be able to do an 'if' on a string? You could interpret it as the
# string's length, or the string's length && string ne "0".
#
# 2. No unless
# 'unless' is often more useful than 'if'.
> So I know for the first-stage rollout, does Apache's module system support
> Apache managing filehandles and modules calling apache's I/O routines, or
> does it just do weird magic with I/O on normal filehandles?
I'm pretty sure that for a simple implementation, we only need to worry
about "
On Sun, 28 Oct 2001, Simon Cozens wrote:
> You are all encouraged to write implementations of the vtable functions
> in scalarclass.c
Cool. So, what needs to get done first? By that I mean, what is standing
in the way of our creating tests for scalar PMCs? Maybe I'm anal
retentive, but I don'
Tom Hughes:
# In message <[EMAIL PROTECTED]>
# "Brent Dax" <[EMAIL PROTECTED]> wrote:
#
# > 4. eq and friends: string variants
# > One thing that seems to be missing is string and numeric
# variants on the
# > comparison ops. While this isn't a problem now, it may be
# once we get
# > P
In message <[EMAIL PROTECTED]>
"Brent Dax" <[EMAIL PROTECTED]> wrote:
> 4. eq and friends: string variants
> One thing that seems to be missing is string and numeric variants on the
> comparison ops. While this isn't a problem now, it may be once we get
> PMCs.
Both string and numeric
I've fixed (I hope) the huge horrible problem whereby vtable_ops was
trying to do pointer arithmetic on struct entries, by making the
multimethod entries into an array of function pointers. I've also
made the vtable functions take a pointer to the interpreter, in case
they need to do any GC stuff.
14 matches
Mail list logo
