Nicholas Clark <[EMAIL PROTECTED]> wrote:
>=item C
Another note: we might as well create a C vtable call as well. We
need some such (and an opcode) anyway for HLL objects.
How could/should that beast look like?
$ python
>>> help(super)
class super(object)
| super(type) -> unbound super object
From: Dan Sugalski <[EMAIL PROTECTED]>
Date: Fri, 29 Apr 2005 15:23:47 -0400
At 10:55 PM -0400 4/28/05, Bob Rogers wrote:
>From: Robin Redeker <[EMAIL PROTECTED]>
>Date: Thu, 28 Apr 2005 00:12:50 +0200
>Refcounting does this with a little overhead, but in a fast and
At 10:55 PM -0400 4/28/05, Bob Rogers wrote:
From: Robin Redeker <[EMAIL PROTECTED]>
Date: Thu, 28 Apr 2005 00:12:50 +0200
Refcounting does this with a little overhead, but in a fast and
deterministic O(1) way.
This is the first half of an apples-to-oranges comparison, and so is
mislead
At 12:37 AM -0400 4/29/05, Uri Guttman wrote:
> "RR" == Robin Redeker <[EMAIL PROTECTED]> writes:
RR> I don't think circular references are used that much. This is
RR> maybe something a programmer still has to think a little bit
RR> about. And if it means, that timely destruction maybe
At 3:05 PM +0200 4/29/05, Leopold Toetsch wrote:
Gerald Butler <[EMAIL PROTECTED]> wrote:
Isn't there something like:
{
my $s does LEAVE { destroy $s } = new CoolClass;
# ... do stuff that may throw ...
}
Or something like that?
Not currently. The
Jerry Gay <[EMAIL PROTECTED]> wrote:
> On 4/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>> 3) Proposal: PIR syntax enhancement
>>
>> .pragma n_operators
>> ...
>> Px = Py + 1
>> ...
>> [EOF]
>>
>> Within this pragma (valid inside and until end of file) the shortcuts
>> '+', '-', ...
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> pmc2c.pl says:
>=item C
> As above, but uses the actual dynamic type of C.
> but for a dynamic class, if I try to use it I get errors such as:
> perl5null.pmc: In function `Parrot_Perl5NULL_set_pointer_keyed_int':
> perl5null.pmc:24: `enum_class_Perl5
On 4/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> 3) Proposal: PIR syntax enhancement
>
> .pragma n_operators
> ...
> Px = Py + 1
> ...
> [EOF]
>
> Within this pragma (valid inside and until end of file) the shortcuts
> '+', '-', ... should translate to "n_add", "n_sub", ...
> Th
pmc2c.pl says:
=item C
Calls the overridden implementation of the current method in the nearest
superclass, using the static type of C.
=item C
As above, but uses the actual dynamic type of C.
but for a dynamic class, if I try to use it I get errors such as:
perl5null.pmc: In function `Parro
Gerald Butler <[EMAIL PROTECTED]> wrote:
> Isn't there something like:
> {
> my $s does LEAVE { destroy $s } = new CoolClass;
> # ... do stuff that may throw ...
> }
> Or something like that?
Not currently. There used to be a C opcode, but I've deleted
it
On Fri, Apr 29, 2005 at 08:14:38AM -0400, Butler, Gerald wrote:
:
: Isn't there something like:
:
: {
: my $s does LEAVE { destroy $s } = new CoolClass;
: # ... do stuff that may throw ...
: }
:
: Or something like that?
Yes,it's
my $s will leave { d
Isn't there something like:
{
my $s does LEAVE { destroy $s } = new CoolClass;
# ... do stuff that may throw ...
}
Or something like that?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Martin D Kealey
Sent:
Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> Is it (yet?) possible to use tailcalls from/to object methods?
Well, there is a C opcode in ops/object.ops. But I don't
know, if it works correctly.
$ find t -name '*.t' | xargs grep tailcall
t/pmc/sub.t:tailcall P0
t/pmc/sub.t:tailcall P0
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: boemmels
> Date: Thu Apr 28 14:29:39 2005
> New Revision: 7942
> Modified:
>trunk/compilers/pge/ (props changed)
>trunk/dynclasses/ (props changed)
>trunk/runtime/parrot/dynext/ (props changed)
> Log:
> Ignore some generated
1) we now have a rather complete set of opcodes that return a new result
PMC, all prefixed by "n_", e.g.
n_add Px, Py, 1
n_abs Px, Py
These opcodes can/should be used by HLLs like Python, which have the
semantics of immutable scalars and newly created result PMCs.
2) Tests for all these opc
Is it (yet?) possible to use tailcalls from/to object methods?
I looked through the various pod files and couldn't find anything,
and I remember seeing some discussion about tailcalls in general
a couple of months ago but didn't stumble across the answers in the
archives.
I'd appreciate any gentle
Nick Glencross <[EMAIL PROTECTED]> wrote:
> Guys,
> This isn't a highly critical segfault I imagine, although it might be of
> interest to someone.
> I discovered 'make fulltest' this evening. One of the debuginfo tests
> (#7) fails as follows with r7942 on i386 Linux:
> [EMAIL PROTECTED] parro
17 matches
Mail list logo
