[Vm-dev] VM endianness

[stephane ducasse]

On 18 Mar 2015, at 20:49, Stefan Marr <smalltalk at stefan-marr.de> wrote:

> 
> 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.

in fact first I would like to reduce the dependencies
then ideally removing all the isLittleEndian test and logic from the image would be good.
> 
> Best regards
> Stefan
> 
> -- 
> Stefan Marr
> INRIA Lille - Nord Europe
> http://stefan-marr.de/research/
> 
> 
>