Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
The 'eval' compiler returns a bytecode segment without a constant table. The
'destroy' of the Eval PMC needs to handle that.
How that? Are there no constants? Anyway, switching to a new bytecode
segment does switch the constant table too, so all
Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
this patch brings Parrot m4 to terms with recent eval changes. The compile
function of the 'eval' compiler now returns an Eval PMC. The m4 macro eval
is a simple interpreter of integer arithmetic expressions.
Thanks, applied.
leo
Leopold Toetsch wrote:
Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
The 'eval' compiler returns a bytecode segment without a constant table. The
'destroy' of the Eval PMC needs to handle that.
How that? Are there no constants? Anyway, switching to a new bytecode
segment does switch the constant
Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
Leopold Toetsch wrote:
How that? Are there no constants?
Yes, there are no constants. The only thing the generated sub does, is
to return an integer value, that was computed in the C-Code.
Thus the m4 macro eval( 1 ^ 3 ) compiles into a sub that
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #32466]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32466
Hi,
this patch brings Parrot m4 to terms with recent eval changes. The
