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
Howto packout _SC / _NC KEYs
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 Sep 10 2002, 6:48 am
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Tue, 10 Sep 2002 12:15:09 +0200
Local: Tues, Sep 10 2002 6:15 am
Subject: Howto packout _SC / _NC KEYs
imcc (0.0.9) has an integrated parrot interpreter and tries to write out
  a PBC file too. Running code succeeds currently for ~95 % of perl6
tests (in half the time ;-).

But I've problems in writing out the .pbc, especially Const_Table, type
PFC_KEY / PARROT_ARG_SC (and _NC if one would use these).

The problem seems to be, that all other key types can be looked up by
key.cache->int_val, but not _SC and _NC as there value is the contents
of another string or number constant.

So packing a packfile seems not to be reversible.

I see currently 3 possible ways to workaround this problem:

1) make another indirection in reading an _SC or _NC key, so that
   key.cache->int_val is the index into the constant table and not the
   string_val or the num_val itself.

2) don't use ->data as the key->next pointer but some structure
    data -> { int idx, PMC *next } and store the constant index there.

3)
The easierst solution (for me): provide the possibility to call a
callback, that fills the packed structure with the required data.
Actually I have also this packed data, because on building the keys I
assemble this packed data, which on PackFile_Constant_unpack_key()
generates all the PMCs for runtime.

1) and 2) would be a general solution but require a major rewrite of key
functions / access and have drawback for speed / memory usage.

3) is "if you want to packout _SC keys, do it yourself" ;-)

Comments welcome,
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 »