After spending a couple of hours looking at Python::Bytecode and the
Python source, I decided I didn't like the module. So I wrote my own.
I decided Bytecode::Python would work nicely for the name, though it's a
bit close to the namespace. I basically redesigned it, so it should be a
little
[ CC'ed all + perl6-internals so fullquote ]
Mark Hahn wrote:
I have been looking over Parrot in consideration as a foundation for
Prothon. Let me give you some of my thoughts and ask another question or
two. Feel free to pass this on to any or all on the Parrot team.
Prothon is a small
[EMAIL PROTECTED] cat f.py
if __name__ == '__main__':
print filter(lambda x: x 5, range(10)), range(5)
$ perl pie-thon.pl f.py | parrot --python -
Have fun,
leo
[snipped except for essentials :) ]
Book News
New Releases
***Perl 6
The Perl 6 Summary for the week ending 2004-07-10
Another week down, another summer summary. On a Monday no less. Last
week I even managed to get the summary to the mailing lists before the
Perl 5 Porters summary. I may have been even more surprised that Rafael
by that. Let's see
1) I've serious troubles with the precision of string_to_num. The test
bewow fails, 1.e100 isn't really 10**100.
2) I've modified string_to_num to just use atof() which works.
3) This makes 2 tests fail (pmc_22, pmc_32). *But* these seem both to be
bogus: I can't imagine that e.g. Z1 should
On Mon, 12 Jul 2004, Leopold Toetsch wrote:
1) I've serious troubles with the precision of string_to_num. The test
bewow fails, 1.e100 isn't really 10**100.
2) I've modified string_to_num to just use atof() which works.
I so wish this were the case. Unfortunately it's not. atof's behaviour
On Mon, Jul 12, 2004 at 09:20:31AM -0400, Dan Sugalski wrote:
On Mon, 12 Jul 2004, Leopold Toetsch wrote:
1) I've serious troubles with the precision of string_to_num. The test
bewow fails, 1.e100 isn't really 10**100.
2) I've modified string_to_num to just use atof() which works.
I so
On Mon, 12 Jul 2004, Nicholas Clark wrote:
On Mon, Jul 12, 2004 at 09:20:31AM -0400, Dan Sugalski wrote:
On Mon, 12 Jul 2004, Leopold Toetsch wrote:
1) I've serious troubles with the precision of string_to_num. The test
bewow fails, 1.e100 isn't really 10**100.
2) I've modified
3) Is there someone on the develpment team who could hold my hand in the
beginning to get me going with Parrot in Visual Studio? After a brief
There isn't a certain someone. Just put your question on the list. Surely it
won't remain unaswered for long, at least as regards the
configuringmaking
On Mon, Jul 12, 2004 at 09:29:23AM -0400, Dan Sugalski wrote:
On Mon, 12 Jul 2004, Nicholas Clark wrote:
On Mon, Jul 12, 2004 at 09:20:31AM -0400, Dan Sugalski wrote:
On Mon, 12 Jul 2004, Leopold Toetsch wrote:
1) I've serious troubles with the precision of string_to_num. The test
Leo --
I had tinkered around with this stuff back in 2003, and ended up writing
Python::Bytecode::SAX to help me visualize bytecode. IIRC, I ran into
the same issue of only disassembling one code block. I'd be interested
to know if P::B::S treats your example python bytecode any better than
P::B.
On Mon, 12 Jul 2004, Gregor N. Purdy wrote:
Leo --
I had tinkered around with this stuff back in 2003, and ended up writing
Python::Bytecode::SAX to help me visualize bytecode. IIRC, I ran into
the same issue of only disassembling one code block.
I've finished up (yay, free time at lunch!)
The last rev of Python::Bytecode is up and available for poking at.
http://www.sidhe.org/~dan/Python-Bytecode-2.3.tar.gz if you want it.
Handles multiple code objects in a file now (woo!) as well as actually
supporting Python 2.1 and 2.2. I think. Tests would be in order, but I
haven't actually
Fixed a bug in the damn thing (that I'd introduced) and fixed the tests to
actually test properly, including both a Python 2.2 and 2.3 format
bytecode file in the archive.
Rather than mail the thing to people *again* I've just stuck it up for web
snagging.
... doesn't know BigInt. You can't format:
Parrot_sprintfc(interp, %Pd, big_pmc)
There are some long modifiers, but they are useles for PMC.s You don't
know the integer size of PMCs. So the whole concept of spf_render,
spf_vtable needs modificatioms to take care of such cases.
I'd say that:
# New Ticket Created by Nicholas Clark
# Please include the string: [perl #30683]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=30683
---
osname= darwin
osvers= 7.0
arch= darwin-thread-multi-2level
cc= cc
Nicholas Clark (via RT) wrote:
It seems that the test is trying to count the number of times the libc
qsort calls the compare function. This doesn't seem like a fantastically
portable idea.
I'm not sure of the easiest way to re-write the test to expect that value to
be non-zero, which seems like
18 matches
Mail list logo
