Dan Sugalski <[EMAIL PROTECTED]> wrote:
> The translation for a number of the python ops depends on whether
> we're going with runtime stack action or compile-time stack->register
> translations.
My experiments[1] show that the latter should be doable, the more because
...
> BINARY_:
>restor
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> ..., it seems worth making:
> new Px
> a synonym for
> new Px, Undef
Makes sense, yes.
leo
Way, *way* behind, but here's my current thinking. Note that a good chunk of
these are as yet blank--I'm running out of caffeine right now. (More to come,
though, but I've waited too long as it is to type in and figure out some of this stuff)
Here's a list of python's opcodes and the translation t
Okay, so as I'm working on the very, very late python bytecode
translation documentation I'm coming across stuff we need to
consider, and this is the first of them: The generic new PMC. (No,
I've not yet finished the doc, nor have I dug through most of the
past few week's mail. First things fir
Where is Python::Bytecode and where is Dan?
leo
The Perl 6 Summary for the week ending 2004-07-04
Another week, another Perl 6 Summary. This is becoming a habit.
Let's do perl6-internals first shall we?
Japhy's Perl 6 rules parser
Last week Jeff 'japhy' Pinyan announced that he'd be working on a Perl 6
rules parser once he'
Leopold Toetsch wrote:
Stas Bekman <[EMAIL PROTECTED]> wrote:
I vaguely remember that perl6 was scheduled to be released in the
fall... Can someone please remind me of which year?
Hi Stas - that's of course next year.
Hi Leo. That's a great news.
Can someone from the perl6 crowd please followup o
Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> The problem seemed to be that no memory is allocated in PIO_reads for the
> string buffer. This can be helped by using the new function
> PIO_make_io_string.
Thanks, applied - except the string change which produces a warning
about pointer math wi
