Re: pugscc --runparrot -e "'Hello, Parrot'.say"

2005-03-26 Thread Autrijus Tang
On Sat, Mar 26, 2005 at 04:44:52PM +0100, Leopold Toetsch wrote: > I had a look at the generated mandel.imc. Remarkable, how compact > Parrot.hs is and what it already does. Thanks. One of my remaining large TODOs before Pugs 6.2.0 is to recode the evaluators in Template Haskell as Compile/Haskel

tcl parser.

2005-03-26 Thread William Coleda
The tcl parser (lib/parse.imc) has been removed and migrated to a method in a PMC. (Anyone looking for a C task could go through and cleanup the parse method in tclparser.pmc - it's basically copied directly from the assembler style with many gotos, no loops, etc. If you make changes, just make

Re: pugscc --runparrot -e "'Hello, Parrot'.say"

2005-03-26 Thread Leopold Toetsch
Autrijus Tang <[EMAIL PROTECTED]> wrote: > As of Pugs revision 1024, this works: > % pugscc --runparrot -e "'Hello, Parrot'.say" I had a look at the generated mandel.imc. Remarkable, how compact Parrot.hs is and what it already does. Some remarks: 1) s__z = s__t # mandel.imc:149 This

Re: [perl #34576] [PATCH] more pmc2c2.pl work

2005-03-26 Thread Matt Diephouse
chromatic <[EMAIL PROTECTED]> wrote: > Is there a specific reason these are comments and not POD? Because there's a large amount of POD at the beginning of the file that targets a different audience. In this instance, I've taken POD to be documentation for PMC writers and comments to be for anyon

Re: [perl #34576] [PATCH] more pmc2c2.pl work

2005-03-26 Thread chromatic
On Fri, 2005-03-25 at 20:49 -0800, Matt Diephouse wrote: > This patch (a) adds comments before each subroutine describing its > parameters, its return values, and what it does, Is there a specific reason these are comments and not POD? -- c