[perl #38964] .sub names can't be Unicode.

2006-04-22 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #38964] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38964 > The following PIR: .sub unicode:"\u" print "ok\n" .end Should print: "ok", but

Re: RFC: Possible SoC Proposal

2006-04-22 Thread Ruben Fonseca
Alberto Simões wrote: > The proposal was to create a compiler to this language. You can check the grammar (well, it might change a little but is mainly the one there) and examples at http://eremita.di.uminho.pt/~ambs/LISS Why it might be interesting: have one more language targeted to Parrot,

Re: Bytecode

2006-04-22 Thread Jonathan Worthington
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: Hey, new guy here. Welcome. :-) I'm really interested in the parrot bytecode. What are the files/dirs I should be looking at to understand everything about packfiles, including layout, api to deal with it, extracting, writing, JIT compiling, et

Re: RFC: Possible SoC Proposal

2006-04-22 Thread Ruben Fonseca
Alberto Simões wrote: Hi This Google Summer of Code proposal was an idea we had when Leopold visited Braga this month to talk about Parrot. He had a talk with a teacher here in the university which teach compilers, and is working on a toy language named LISS (Language of Integers, Sets and S

Bytecode

2006-04-22 Thread [EMAIL PROTECTED]
Hey, new guy here. I'm really interested in the parrot bytecode. What are the files/dirs I should be looking at to understand everything about packfiles, including layout, api to deal with it, extracting, writing, JIT compiling, etc. I took a look at the parrot bytecode format page, at parrot

Re: [perl #38957] hash test failures

2006-04-22 Thread Matt Diephouse
Will Coleda <[EMAIL PROTECTED]> wrote: > I'm using gcc 4.0.1, an '--optimized' Configure, and perl 5.8.6 Ahh. When I do an '--optimized' Configure, I get a bunch of failed tests. The hash tests are still passing, but that may be coincidental. -- matt diephouse http://matt.diephouse.com