[M3devel] Modula-3 bitfields
mika at async.caltech.edu
Sat Aug 25 23:55:19 CEST 2012
>I am in no doubt about general inadequacies of C et al=85
>What I hate is an idea of setters and getters for my bitfields. With =
>pragma, compiler generated load/store will behave as needed. Everything =
>transparent and just-working.
Until you have some data that is PDP-endian :-)
Or want to split a field across a boundary that you're not supposed to
be able to split a field across.
Or have a field that's semantically scattered/gathered.
Can your proposed scheme represent IEEE floating point?
I agree it is a very useful idea, I agree it has to be done "right".
But my definition of doing it "right" would be so demanding you'd be
crazy to do it in the compiler....
>Divided by a common language
>dragisha at m3w.org
More information about the M3devel