Jerome Quelin (via RT) wrote:
# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19610]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19610 >
- currently I'm just printing on stdout the resulting
Nicholas Clark wrote:
base_vtable ... name, type, ...
var_vtable ... get_integer, set_integer, ...
val_vtable ... add, sub, ...
prop_vtable ... property functions (set/getprop are different, depending
on the existence of the property hash)
The vtable pieces and the _vtable conta
On Mon, Dec 30, 2002 at 11:45:19PM +, Nicholas Clark wrote:
> Indeed. However, when I tried compiling my Ook! test program:
> I got this:
>
> Label KOO1_2 already exists at ../../assemble.pl line 557.
>
> (admittedly from a pre-built parrot that is about 2 weeks old)
Also on a clean checko
Many of our tinderbox failures result from architecture-specific
shortcomings in our current root set scanning code. The whole
stackwalk/register scan is also rather slow, as Peter Gibbs showed a
few decades back. (Okay, so it was probably only about a year ago.) In
pondering the problem, I found m
On Mon, Dec 30, 2002 at 11:09:07PM +, Jerome Quelin wrote:
> Ok, about this implementation:
> - this is a compiler (and not an interpreter) that spits Parrot
> assembly code (yes, I'm targeting Parrot).
> - it implements every Ook! instruction but the "Ook. Ook!" one. I'll
> work on it late
# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19610]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19610 >
Thanks to our dear summarizer, I'm now known (from a googlism point of
view) as 'one o
On Mon, Dec 30, 2002 at 04:36:31PM +0100, Leopold Toetsch wrote:
> - a "variable" consists of 3 parts: name, variable, value
> - the 2 latter are now handled in one go in our vtable funcs
> - variable and value access should be separate operations (think tie)
> - 2-stage access (get_var->value->ge
On Mon, Dec 30, 2002 at 05:24:56PM +, Jerome Quelin wrote:
> Upon general (ahem) request, the befunge interpreter now supports
> breakpoints inside the debugger.
Thanks, applied
Nicholas Clark
Jerome Quelin (via RT) wrote:
# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19599]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19599 >
Hi,
How one can delete a key from a perl hash in parro
Dan Sugalski wrote:
At 11:45 AM +0100 12/30/02, Leopold Toetsch wrote:
A "simple" PMC would be a typical scalar (num or int) without
properties. Attaching properties to such a PMC would need promoting it
to a "complex" PMC.
We can't promote to a larger type, as that would require moving th
# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19603]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19603 >
Upon general (ahem) request, the befunge interpreter now supports
breakpoints inside t
# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19599]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19599 >
Hi,
How one can delete a key from a perl hash in parrot assembly?
I tried:
new P0,
At 11:45 AM +0100 12/30/02, Leopold Toetsch wrote:
This is the next step in using a common PObj for Buffers/PMCs. The
major change is: free_unused_pobjects is now the common header
freeing function working on all Buffer & PMC headers.
Object specific destroying is done in free_unused_pobjects t
...
*) Spec the vtable changes
...
The variable/vtable stuff should be done in the next day or two.
More threads with $subject:
- Variable/Value split prelims
- [RFC] Buffer/PMC unification, variable/value split, tied scalars
As "the next day or two" is almost gone, I would like to summarize th
[EMAIL PROTECTED] (via RT) wrote:
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #19493]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19493 >
Thanks - applied,
leo
This is the next step in using a common PObj for Buffers/PMCs. The major
change is: free_unused_pobjects is now the common header freeing
function working on all Buffer & PMC headers.
Object specific destroying is done in free_unused_pobjects too. Washing
memory for PMCs is still in add_free_pm
16 matches
Mail list logo
