On Mar 19, 2015, at 8:17 AM, Bert Freudenberg bert@freudenbergs.de wrote:
On 18.03.2015, at 20:49, Stefan Marr smalltalk@stefan-marr.de wrote:
Hi:
On 18 Mar 2015, at 20:17, tim Rowledge tim@rowledge.org wrote:
On 18-03-2015, at 12:10 PM, Eliot Miranda eliot.miranda@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?
+1
This is only needed if you work around the VM, like when you use FFI. So IMHO the FFI plugin should support that primitive. Or maybe it does? Doesn't it provide special bytearray accessors?
Yes. Given FFI primitives its easy to construct a test out of longAt:put: and byteAt:. I didn't state it earlier cuz the prims aren't in the base VM.
- Bert -