Hallo Martin, Du schriebst am Sat, 9 Nov 2013 20:31:58 +0100:
> Your suggestion how to define the bit size of a type? Well, specify the requested number of bits together with the bitfield's identifier. There's a host of notations in use, e.g. the C-ish "<name>: <bits>", or a functional expression "<name> (<bits>)" or something like Delphi's string or array length spectification: "<name> [<bits>]". Or even a notation that includes the exact location of the field as used by hardware register field definitions sometimes: "<name> <highbit>:<lowbit>". > > On the other hand, your invention of the new keyword "bitpacked" looks > > quite good to me, as it makes clear that this record definition ... > No invention, FPC has it already. Well, yes, the keyword, but it's rather useless: "Note that the internals of the bitpacking are opaque: they can change at any time in the future. What is more: the internal packing depends on the endianness of the platform for which the compilation is done, and no conversion between platforms are possible..." > > My suggestion: if you're going to implement such a thing, use it. > > (The "bitpacked" keyword, i.e.) > > > I don't understand. Huh? What's so hard to understand if I say, if you're going to provide bitpacked records, use the keyword to declare them? Should I say it in german? -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
