On 11/13/2013 05:35 PM, Martin Schreiber wrote: > Then you will be banned from developing security relevant software. ;-)
Do you intend to implement runtime range checking with any of these types ? While as an option, this of course is great, but I think for performance sake it should not always be done. Especially with this "simulated bit fields" this is not at all what I would want. Maybe some syntax for could be provided that not explicitly defines a range and switches off range checking. This seems rather intuitive to me. e.g. type record ty = bitpacked record x5: 0..3: 2 x6: unsigned : 2; // same as x5, but switching off runtime range checking for x6 x7: -2..1: 2 x8: signed : 2; // same as x7, but switching off runtime range checking for x8 end; -Michael ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk