[Vm-dev] VM endianness
Stefan Marr
smalltalk at stefan-marr.de
Wed Mar 18 19:49:10 UTC 2015
Hi:
> On 18 Mar 2015, at 20:17, tim Rowledge <tim at rowledge.org> wrote:
>
> On 18-03-2015, at 12:10 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>>
>> At least it doesn't use BitBlt. Its got much less dependencies than the existing code and is much simpler. Isn't that worth something?
>
> No need to use Bitmap if that’s a real problem - make a trivial class that is ArrayedCollection variableWordSubclass:#EndianTestThing and use that.
Shouldn’t the VM should abstract from such things? Why is there a need for this knowledge on the application side?
I guess, it is needed for low-level hacking at the language level?
But even if there is a good use case, this is information about the underlying system, and the VM should at least mediate reliably with a proper interface. All other solutions rely on an undefined implicit interface.
Best regards
Stefan
--
Stefan Marr
INRIA Lille - Nord Europe
http://stefan-marr.de/research/
More information about the Vm-dev
mailing list