RE: [boost] A problem concerning msvc++ and boost::spirit::phoenix

2003-06-19 Thread Michael Walter
Visual C++ 6.0 doesn't support partial template specialization. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of DudeSan > Sent: Thursday, June 19, 2003 3:27 PM > To: [EMAIL PROTECTED] > Subject: [boost] A problem concerning msvc++ and boost::spirit::

[boost] Spirit example typo

2003-06-18 Thread Michael Walter
In http://www.boost.org/libs/spirit/doc/number_list.cpp.html, using namespace spirit should read using namespace boost::spirit; I think. Apologies if this is the wrong list for such an unimportant report ;) - Michael ___ Unsubscribe & other changes:

Re[2]: [boost] int vs int32_t [was: Serialiization Review repostwith consistent quoting]

2002-11-27 Thread Michael Walter
KL> 2) Although both POSIX and C99 define them to be 2's complement integers KL> with the appropriate number of bits, neither standard sets a requirement KL> on byte ordering within the multibyte types. Thus, even if a platform KL> supports them (say, the BSD family), the binary form of the inte

Re[2]: [boost] int vs int32_t [was: Serialiization Review repostwith consistent quoting]

2002-11-27 Thread Michael Walter
>> If you aim for portability, you can simply use int8_t, int16_t, etc. >> in your implementation - no need to use it in the archive interfaces >> as far as I get it. Sorry if I miss the point :) > If a library user wants his archives to be portable he has to use > int8_t, int16_t, etc.. for all da

RE: [boost] int vs int32_t [was: Serialiization Review repost withconsistent quoting]

2002-11-26 Thread Michael Walter
DG> Robert Ramey wrote: >> We should discuss whether to use short, int, long ... as the primitive >> types or int8_t, int16_t, int32_t, int64_t. The latter makes it easier >> to write portable archives, the former seems more natural. I can >> accept both choices but we should not mix the two as