Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
eval changes
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Leopold Toetsch  
View profile  
 More options Nov 9 2004, 12:18 pm
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Tue, 09 Nov 2004 18:18:05 +0100
Local: Tues, Nov 9 2004 12:18 pm
Subject: [CVS ci] eval changes
Print | Individual message | Show original | Report this message | Find messages by this author
There is of course no "eval" in Parrot. Anyway:

* the signature of a Parrot compiler PMC is now "PIt" - it returns
   a Sub PMC directly - or more precisely an Eval PMC, which is a
   Closure
* attached onto this Closure is the compiled bytecode
* this Closure's are named EVAL_n (n = 1...)
* it can (or has to) be invoked like any other sub according to calling
conventions.
* this also means that the compiled code has to end with "invoke P1".
* compiled code that just "end"s terminates the run-loop
* the compiled code has the life-time of the returned Sub PMC

TODOs:
* implement the @MAIN and @LOAD pragmas
* provide an @ANON pragma, so that globals are not effected by compiled
    subroutine names
* adjust imcc tests
* cleanup

The forth compiler snippet works with s/end/invoke P1/ for the compiled
code.

see t/pmc/eval.t for examples

leo


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google