> > int1 > > int2 > > int4 > > int8 > > int16 > > int32 (aka int on 32-bit machines) > > int64 (aka int on 64-bit machines) > > Ok, so Parrot doesn't have those. Parrot has "int".
I think it should have those, but I'm not a Parrot developer, I've jused used PIR. But I have used a few other VMs in this application and have found explicit integer sizes useful. For example JADE (an amazing math/physics/units/sycro Java library): http://jade.dautelle.com/api/overview-summary.html Has real-time (do not cause Java new or free, removing GC) numerics based on shared in context pools, that can be freed or reused. Its numbers heirarchy is: http://jade.dautelle.com/api/jade/math/numbers/package-summary.html The Ficl VM also has specific interger sizes that at least made the machine more easy to understand: http://ficl.sourceforge.net/ > How would Parrot expect languages to implement such features? Should > there be a set of (highly JIT-optimizable) PMCs that present sized > type > features, Yes, again, not a developer. > should the core register types be sizable somehow or should > languages just be left to roll their own PMCs that do whatever they > want? The second would definately put the burden on the language designer. -Michel
