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
Message from discussion Loading bytecode at runtime
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 Feb 20 2004, 6:49 am
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Fri, 20 Feb 2004 09:42:04 +0100
Local: Fri, Feb 20 2004 3:42 am
Subject: Re: Loading bytecode at runtime
Print | View thread | Show original | Report this message | Find messages by this author

Dan Sugalski <d...@sidhe.org> wrote:
> Okay, since folks are diving into IMCC (assuming we can keep a fight
> from breaking out) it's time to address bytecode loading.
> We've got the need to have subs that get executed when a code segment
> is loaded, a need to have a 'main' sub that gets executed as mainline
> code, and subs that get executed after compilation but before run.
> So, since I *hate* magic name subs, what I want to do is add tags to
> subs to indicate what they should do. So, these tags are what I want,
> to be added to the .pcc_sub line:
> MAIN
> IMMEDIATE
> LOAD
> POSTCOMP

Started that now:

The syntax (proposed and current) is for PASM:

  .pcc_sub @MAIN _main:

and for PIR:

  .sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP

albeit it doesn't make much sense, to through all possible pragmas at
one sub ;)

All these specifiers are optional.

I did choose the '@' prefix because of possible name collisions with
existing labels (like t/op/string_102.pasm). It clearly denotes that
something special is going on here.

Next will be @LOAD and possibly @MAIN functionality.

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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google