As a response for a request for sub integers, in the document I will delete the is_even and is_odd member functions, and add: const integer highest_bit() const; const integer lowest_bit() const; const integer get_sub( const integer &, const integer & ) const; By the way here no size_type is used, because size_type suffices for the range of bytes, but not for the range of bits, which is a factor 8 larger. Regards, Maarten. "Maarten Kronenburg" <M.Kronenburg@inter.nl.net> wrote in message news:e55e0m$jnh$1@sea.gmane.org...
Jarrad, About the sub integers I was a little too easy, because my solution is not as fast as extracting sub integers. What you ask for is what substr is for strings. Now I think this should be added for performance reasons. Regards, Maarten.
"Jarrad Waterloo" <jwaterloo@dynamicquest.com> wrote in message news:20060524184833.5667B14A8001@dqmail.dynamicquest.com...
Here are my comments concerning Maarten's infinite precision integer draft. I would not wait to submit this library to boost before these following features because people are in need of it now.
1) The ability to extract sub integers out of an integer such as the integer at bit offset 3 and length of 4. This is especially helpful in the area of RFID where large unsigned integers are partitioned into smaller integers. 2) The ability to convert integer to bases other than base 10; any really from base 2-36 3) An implementation of a fixed sized stack version of the integer_allocator. This may be useful for performance when someone is not working with an infinite precision integer but a very large one such as 512 or 1024 bits. 4) An unsigned version of the integer class that benefits from the higher performance of unsigned operations
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost