On Tuesday, November 25, 2014 8:49:46 AM UTC-8, Seth Berman wrote:
I wanted to get you an answer...thought I'm not sure its the best one because I haven't been in this area a whole lot.
Thanks, Seth. It's appreciated.
It looks like IndirectInstVars comes into play when packaging an image. I guess with IC read-only segments and the fact that a runtime can have multiple ICs, there is a problem to solve involving objects referring to each other across boundaries. This IndirectInstVars seems to provide a central registry where these can be accessed and during packaging I see that bytecodes are rewritten such that the slots read/store indexes into this table which then get the actual value.
That does sound sensible.
Looking at packager code makes my eyes bleed and puts me in a bad mood...so I had to stop:) Just consider this a best guess for the moment.
I agree ... and sympathize.
Thanks again.
-- Seth
On Friday, November 21, 2014 5:43:40 PM UTC-5, Richard Sargent wrote:
I came across this class variable. I was wondering what it was all about.
Is there anyone at Instantiations who knows and wants to tell? :-)
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To post to this group, send email to
[hidden email].
Visit this group at
http://groups.google.com/group/va-smalltalk.
For more options, visit
https://groups.google.com/d/optout.