- Boost - lists.boost.org

[integer] Extending integer.hpp to 64 bits
by Phil Endecott 15 Apr '07

15 Apr '07

Dear All, Searching the list archive reveals several previous discussions of extending boost::int_t<N> to work with sizes up to 64 bits. These were all several years ago when there may have been compiler issues that made this complex. Would it be true to say that today int64_t is sufficiently widely available that it could be used in integer.hpp? I have hacked a local copy to work with int64_t. Patch follows. Any comments? Phil. --- /usr/include/boost/integer.hpp 2004-08-15 11:13:49.000000000 +0100 +++ integer.hpp 2007-04-14 11:06:11.000000000 +0100 @@ -6,6 +6,8 @@ // See http://www.boost.org/libs/integer for documentation. +// Hacked by Phil Endecott to add 64 bits + // Revision History // 22 Sep 01 Added value-based integer templates. (Daryle Walker) // 01 Apr 01 Modified to use new <boost/limits.hpp> header. (John Maddock) @@ -15,10 +17,11 @@ #ifndef BOOST_INTEGER_HPP #define BOOST_INTEGER_HPP -#include <boost/integer_fwd.hpp> // self include +#include "./integer_fwd.hpp" // self include #include <boost/integer_traits.hpp> // for boost::integer_traits #include <boost/limits.hpp> // for std::numeric_limits +#include <boost/cstdint.hpp> namespace boost { @@ -33,17 +36,19 @@ // convert category to type template< int Category > struct int_least_helper {}; // default is empty - // specializatons: 1=long, 2=int, 3=short, 4=signed char, - // 6=unsigned long, 7=unsigned int, 8=unsigned short, 9=unsigned long - // no specializations for 0 and 5: requests for a type > long are in error - template<> struct int_least_helper<1> { typedef long least; }; - template<> struct int_least_helper<2> { typedef int least; }; - template<> struct int_least_helper<3> { typedef short least; }; - template<> struct int_least_helper<4> { typedef signed char least; }; - template<> struct int_least_helper<6> { typedef unsigned long least; }; - template<> struct int_least_helper<7> { typedef unsigned int least; }; - template<> struct int_least_helper<8> { typedef unsigned short least; }; - template<> struct int_least_helper<9> { typedef unsigned char least; }; + // specializatons: 1=int64_t 2=long, 3=int, 4=short, 5=signed char, + // 7=uint64_t 8=unsigned long, 9=unsigned int, 10=unsigned short, 11=unsigned char + // no specializations for 0 and 6: requests for a type > 64 bits are in error + template<> struct int_least_helper<1> { typedef int64_t least; }; + template<> struct int_least_helper<2> { typedef long least; }; + template<> struct int_least_helper<3> { typedef int least; }; + template<> struct int_least_helper<4> { typedef short least; }; + template<> struct int_least_helper<5> { typedef signed char least; }; + template<> struct int_least_helper<7> { typedef uint64_t least; }; + template<> struct int_least_helper<8> { typedef unsigned long least; }; + template<> struct int_least_helper<9> { typedef unsigned int least; }; + template<> struct int_least_helper<10>{ typedef unsigned short least; }; + template<> struct int_least_helper<11>{ typedef unsigned char least; }; // integer templates specifying number of bits ---------------------------// @@ -53,6 +58,7 @@ { typedef typename int_least_helper < + (Bits-1 <= std::numeric_limits<int64_t>::digits) + (Bits-1 <= std::numeric_limits<long>::digits) + (Bits-1 <= std::numeric_limits<int>::digits) + (Bits-1 <= std::numeric_limits<short>::digits) + @@ -67,8 +73,8 @@ { typedef typename int_least_helper < - 5 + - (Bits <= std::numeric_limits<unsigned long>::digits) + + 6 + + (Bits <= std::numeric_limits<uint64_t>::digits) + (Bits <= std::numeric_limits<unsigned int>::digits) + (Bits <= std::numeric_limits<unsigned short>::digits) + (Bits <= std::numeric_limits<unsigned char>::digits) @@ -80,11 +86,12 @@ // integer templates specifying extreme value ----------------------------// // signed - template< long MaxValue > // maximum value to require support + template< int64_t MaxValue > // maximum value to require support struct int_max_value_t { typedef typename int_least_helper < + (MaxValue <= integer_traits<int64_t>::const_max) + (MaxValue <= integer_traits<long>::const_max) + (MaxValue <= integer_traits<int>::const_max) + (MaxValue <= integer_traits<short>::const_max) + @@ -93,11 +100,12 @@ typedef typename int_fast_t<least>::fast fast; }; - template< long MinValue > // minimum value to require support + template< int64_t MinValue > // minimum value to require support struct int_min_value_t { typedef typename int_least_helper < + (MinValue >= integer_traits<int64_t>::const_min) + (MinValue >= integer_traits<long>::const_min) + (MinValue >= integer_traits<int>::const_min) + (MinValue >= integer_traits<short>::const_min) + @@ -107,12 +115,13 @@ }; // unsigned - template< unsigned long Value > // maximum value to require support + template< uint64_t Value > // maximum value to require support struct uint_value_t { typedef typename int_least_helper < - 5 + + 6 + + (Value <= integer_traits<uint64_t>::const_max) + (Value <= integer_traits<unsigned long>::const_max) + (Value <= integer_traits<unsigned int>::const_max) + (Value <= integer_traits<unsigned short>::const_max) +

2 1

[ublas] warnings
by Steven Watanabe 15 Apr '07

15 Apr '07

AMDG Sigh. msvc doesn't recognize explicit destructor calls as using a variable, causing warning C4100: 'i' : unreferenced formal parameter at storage.hpp line 274, CVS-HEAD In Christ, Steven Watanabe

1 0

[io_state_savers] warnings
by Steven Watanabe 15 Apr '07

15 Apr '07

AMDG Because the io_state_savers hold a reference to the ios_base, msvc gives me warning 4512 assignment operator could not be generated. Please either declare an assignment operator, use pointers instead of references, or explicitly suppress this warning. In Christ, Steven Watanabe

1 0

[Boost-bugs] [ boost-Bugs-1700837 ] mutli_array/types.hpp 64-bit types?
by SourceForge.net 15 Apr '07

15 Apr '07

Bugs item #1700837, was opened at 2007-04-14 17:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1700837&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mutli_array/types.hpp 64-bit types? Initial Comment: multi_array/types.hpp currently: // needed typedefs typedef std::size_t size_type; typedef int index; Should /index/ be a 64-bit quantity? Should it be std::ptrdiff_t or std::size_t? I caught this because of warnings from MS Visual Studio 8 (2005). Boost is really great! Thanks! Sincerely, Mike Albert m_albert137(a)yahoo.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1700837&group_… ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Spirit2 cookbook example suggestions welcome
by Joel de Guzman 14 Apr '07

14 Apr '07

ebo(a)sandien.com wrote: > Joel de Guzman <joel(a)boost-consulting.com> said: > >> ebo(a)sandien.com wrote: >> >> EBo! So nice to see you every now and then. > > Joel! You always make me feel so welcome ;-) > >>> Something I was playing around with a couple of years ago and never took the >>> project to full production was a user extensible machine-tool parser which >>> kept the rules and the grammar in persistent dynamically loadable objects. I >>> was able to load new commands on the fly, or actually change the grammar rules >>> themselves... >>> ... >>> Would something like that be interesting? >> Yeah, that's cool! I'm not sure it fits the criteria I outlined though. > > I'll review the criteria tomorrow... > >> Seems to be too complex for the cookbook? > > How many lines/pages of code and description is reasonable? The entire > framework for the above is something like 1,750 lines of code, but that > includes the dynamic parser and 28 RS-274 M and G codes. Stripped down for a > minimal example could be a fraction of that. Anyway, maybe we can come up > with something appropriate. I'm thinking more in the tune of a few lines of grammar here and there -- small enough to digest in a few minutes. Something like... if you want to do something like this, you write something like this. Example: "I want to parse pascal style strings where the first byte is the length (N) of the string, followed by N characters. How do you do it?" Of course that's a very simple example. We have more elaborate examples like "How do you write a C-like language and a virtual machine?". We have that. Now, I want some more in-betweens. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

1 0

[Boost-bugs] [ boost-Bugs-1700790 ] grammatical error in error message
by SourceForge.net 14 Apr '07

14 Apr '07

Bugs item #1700790, was opened at 2007-04-14 14:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1700790&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: test Group: release 1.34.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Beman Dawes (beman_dawes) Summary: grammatical error in error message Initial Comment: BOOST_TEST_MESSAGE( "Test case has less failures then expected" ); Should be BOOST_TEST_MESSAGE("Test case has fewer failures than expected" ); The word "fewer" is needed because the statement is dealing with quantity of distinct objects or concepts. The word "less" would be used for volumes or amount of one distinct object or concept. The word "then" is for if-then statments not for comparison. in the file results_collector.ipp revision 1.5. Sincerely, Mark Barkell ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1700790&group_… ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

boost::freetype - extension for boost::gil
by Tom Brinkman 14 Apr '07

14 Apr '07

>> source-code I'm working on it again this weekend. If anyone wants to see it now, just email me. Otherwise, I'll upload an updatted version by monday. An earlier provided link does not work. Here is where the gil extension code is being hosted. http://code.google.com/p/gil-contributions/

1 0

boost::freetype - extension for boost::gil
by Tom Brinkman 14 Apr '07

14 Apr '07

The adobe developers have indicated that they will be distributing the "gil" extensions with their distribution. In your opinion, what level of scrutiny should the "gil" extensions recieve? Are full reviews warrented for the smaller extensions, which is where I would include my freetype wrapper.

2 1

[optional] New RC_1_34_0 regression
by Richard Smith 14 Apr '07

14 Apr '07

I've just found what I believe to be a new regression on the boost RC_1_34_0 branch relative to the 1.33.1 release. The example below is a simplified extract of some real world where the behaviour of boost::none silently changes. #include <string> #include <iostream> #include <boost/optional.hpp> #include <boost/none.hpp> namespace sql { void literal( std::ostream& os, int i ) { os << i; } void literal( std::ostream& os, boost::optional<std::string> const& str ) { // escaping removed for clarity if (str) os << '"' << str.get() << '"'; else os << "NULL"; } } int main() { sql::literal( std::cout, boost::none ); } In 1.33.1, this prints out 'NULL' (which is what I would naively expect); on 1.34, it prints '0'. In both cases compiles cleanly in gcc 4.1.1. Sorry if this is a known regression, but having just seen the email saying RC_1_34_0 is down to zero regressions, I thought a quick-heads up was in order. Richard

13 33

[math toolkit] Formal Review today, April 11, through April 20
by Tom Brinkman 14 Apr '07

14 Apr '07

Its entirely up to Matthias. If he thinks more time is needed for a proper review of the library, beyond even the extension date, it appropriate to add days, as many as are needed. If it gets to long however, we might consider overlapping it with the next review, in this case the GUID library. The "ten" day period is just a rule of thumb and entirely flexible. Large libraries will often need more days for the review.

3 3