[M3devel] [M3commit] CVS Update: cm3

[Dragiša Durić]

I've worked with both runtimes at this level (but not lately). And I can't think of one reason why this would be correct. (It does not make me right, I know:). Structures are equivalent, IIRC, primary difference being in algorithm. Incremental RTLinker operation results in possible reallocation of type structures (bottom of the world, you-are-the-wizard-if you-read-this), but they are still "static" for the most of (99.999..%) process lifetime.

Question is important and I am sure it is fixable, if only we can identify problem here. There is nothing inherent to ability for dynamic loading demanding bad data structures at the botom of M3 world. Only (not-improbable) sub-optimal decisions made by cmass people at the moment. 

On Jun 7, 2012, at 10:35 PM, Mika Nystrom wrote:

> Sorry, "static" was (slightly) the wrong word.
> 
> I believe they are malloced as an array during program startup.  There is
> something significant about the ordering of this array, which is why you
> can't just add types to the PM3 environment during runtime.  CM3 uses
> more indirection, so it's much easier to add things while running,
> but it also makes TYPECASE, ISTYPE, etc., slower.  Possibly NARROW
> (explicit as well as implicit) as well...
> 
>     Mika

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120608/da6cb95f/attachment-0002.html>