Benjamin Goldberg [EMAIL PROTECTED] wrote:
I would suggest the opnames/categories mutate, alias, and create.
IMHO, we could leave PASM syntax as it is and create opcode aliases
inside the assembler ...
I believe that the most in^H^H logical shorthand spellings of these
opcodes would be :=,
Nicholas Clark wrote:
On Thu, Aug 07, 2003 at 05:21:11PM +0200, Jos Visser wrote:
fortytwo I0
Shouldn't it be the what_do_you_get_if_you_multiply_six_by_nine op?
Shouldn't it be the
what_do_you_get_if_you_multiply_six_by_nine_then_subtract_twelve op?
Nicholas Clark
SCNR2, leo
I hopefully got the semantics of assign Px,Py right now. The LHS gets
the value of RHS, eventually morphing itself to the source type.
Anyway:
assign Px, {Iy,Sy,Ny}
are not needed IMHO, these end up as set_type_native and are identical
to set Px, {Iy,Sy,Ny}.
But we are missing keyed
At 1:35 PM -0400 8/5/03, Michal Wallace wrote:
On Tue, 5 Aug 2003, Joseph Ryan wrote:
Okay, I don't have a good syntax in mind yet,
the point is it's a template language and you
can subclass/override/extend the template.
Maybe there's no syntax and it just uses
cleanly coded classes in some
On Thu, 7 Aug 2003, Dan Sugalski wrote:
haskell_parser - ast - pirate - parrot_code -- imcc - pbc
^
|
parrot_code__templates
So the haskell
Lars Balker Rasmussen (via RT) [EMAIL PROTECTED] writes:
# New Ticket Created by Lars Balker Rasmussen
# Please include the string: [perl #23025]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23025
There's no
