August 2008 - Boost-users - lists.preview.boost.org

just plain weirdness (serialization)
by Noah Roberts 14 Aug '08

14 Aug '08

I'm working with 1.33.1 here and can't upgrade at this point. I'm trying to compile something I compile with VS using mingw. I'm running into this weird problem. The code in question saves and loads a boost::array to an archive. In visual studio the project compiles. With mingw it does not and issues an error about boost::array<double, 4u> not having a serialize member function. So in an effort to try and trick down why it is working fine in visual studio I decided to make a minimal program that saves a boost::array to an archive. I get the same error... I'm trying to include every system file and boost header that would be included but I can't seem to make anything work. Has anyone any idea at all? I've been working on this for a few hours now and just cannot get a minimal program to compile, yet I've compiled the original project many times in VS...including several times today. At a loss here...

3 3

[boost.python] setting member function for creating python objects
by Olaf Peter 14 Aug '08

14 Aug '08

Hi, for my redirected output boost.python (bpl) program I like to set special writing functions at construction time. The idea is to use a boost.function for this, like (my won't work): static std::auto_ptr<stdout_redirector> make_stdout_redirector(EmbeddedPython& console) { std::auto_ptr<stdout_redirector> ptr(new stdout_redirector); *ptr.m_write_fn = boost.bind(EmbeddedPython::write, &console); return ptr; } or even: static std::auto_ptr<stdout_redirector> make_stdout_redirector(EmbeddedPython& console) { std::auto_ptr<stdout_redirector> ptr(new stdout_redirector(boost.bind(EmbeddedPython::write, &console))); return ptr; } using the constructor, which would be different for that what python would see (here comes my idea using bpl::make_constructor into play). So each time my redirector is called, EmbeddedPython::write can call the underlying (not seen here, std::cout used here for simplicity) write instance. The problem: I can not make those calls from boost.python's class_ , isn't it? Any ideas for this? I don't want to use global variables. Thanks, Olaf

1 0

[Serialization] BOOST_CLASS_EXPORT_GUID related compile errors on Boost 1.35 with Visual Studio 2005
by Paul Wais 14 Aug '08

14 Aug '08

Dear List, I am writing to request advice about a compile error possibly related to the BOOST_CLASS_EXPORT_GUID macro under Boost 1.35 and Visual Studio 2005. I unfortunately cannot share much about the cause of the error and was hoping to query the community to see if anybody else has had similar difficulties. In particular, it seems at least one other developer has had a similar problem, as described in the blog post: http://www.alexmccarthy.net/archives/2008/06/16/upgrading-to-boost-135 The problem in question involves a library we wrote that uses basic features of Boost Serialization for marshaling objects to XML. The library compiles and runs successfully on Linux (gcc version 4.2.3 Ubuntu 4.2.3-2ubuntu7). When compiling the same code on a properly-configured Windows machine using Visual Studio 2005, we observe the following compile errors: C:\Boost\include\boost-1_35\boost/serialization/type_info_implementation.hpp(48) : error C2027: use of undefined type 'boost::serialization::extended_type_info_impl<T>' with [ T=boost_time ] C:\Boost\include\boost-1_35\boost/serialization/export.hpp(75) : see reference to class template instantiation 'boost::serialization::type_info_implementation<T>' being compiled with [ T=boost_time ] .\ConstraintSystem/Time/boost_time.h(159) : see reference to class template instantiation 'boost::archive::detail::guid_initializer<T>' being compiled with [ T=boost_time ] C:\Boost\include\boost-1_35\boost/serialization/type_info_implementation.hpp(49) : error C2146: syntax error : missing ',' before identifier 'type' C:\Boost\include\boost-1_35\boost/serialization/type_info_implementation.hpp(49) : error C2065: 'type' : undeclared identifier C:\Boost\include\boost-1_35\boost/serialization/type_info_implementation.hpp(50) : error C3203: 'identity' : unspecialized class template can't be used as a template argument for template parameter 'F2', expected a real type C:\Boost\include\boost-1_35\boost/serialization/type_info_implementation.hpp(50) : error C2955: 'boost::mpl::identity' : use of class template requires template argument list C:\Boost\include\boost-1_35\boost/mpl/identity.hpp(26) : see declaration of 'boost::mpl::identity' . . . (dozens of similar errors follow) The owner of the aforementioned blog suggests to add the line: #include <boost/serialization/extended_type_info_typeid.hpp> to the file: boost/serialization/export.hpp. We have done that and our compile errors go away. Though this fix seems to work for our needs, we endeavor to keep the copy of our Boost library free from unofficial patches. Might anybody have similar troubles? Might there be an "official" fix to this problem? Thank you for your time and I greatly appreciate any help on this issue. Best Regards, -Paul Wais

2 1

[fusion] Why no multi{map,set} ?
by John C. Femiani 14 Aug '08

14 Aug '08

Hi, I was just wondering why fusion (and mpl) don't include multi-maps or multi-sets. Are they unnecessary at compile time? Are they too trivial? Do they conceptually not work? Thanks, John Femiani.

3 3

boost including problem
by szurilo 14 Aug '08

14 Aug '08

Dear all! I have a small library developed in c++ and i would like to invoke some boost function. I develop under Windows XP, Code::Blocks, MinGW 5.1.3 I would like to use some separately built part of boost, like thread and regex. I also built these libs with mingw. So i try to configure my IDE to prepare for boost. I set the compiler search path to C:\Program Files\boost\boost_1_33_1 Is it enough or should i link to thread and regex libs directly to my library? For example: C:\Program Files\boost\boost_1_33_1\bin\boost\libs\regex\build\libboost_regex.lib\gcc\debug\threading-multi\libboost_regex-gcc-mt-d-1_33_1.lib; Isn't it a problem for MinGW to find this lib with the white space character inside "Program Files"? Thanks, Szurilo -- View this message in context: http://www.nabble.com/boost-including-problem-tp18980213p18980213.html Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[gil] More tiff problems
by John C. Femiani 14 Aug '08

14 Aug '08

I found a bug in GIL, and I think I have a patch for it. Basically the tiff reading code in GIL fails to handle alpha channels properly. Basically an RGBA tiff can be read into an RGB image, causing garbage. The source of the problem seems to be that TIFFTAG_PHOTOMETRIC is the only thing used to decide which pixel format to read. One should also read TIFFTAG_SAMPLESPERPIXEL to see if there are any extra fields, and TIFFTAG_EXTRASAMPLES to figure out what they mean. (I did not do all that in this little patch). On a related note: 1) Is GIL updating the boost/SVN repository? It seems to have been a long time (6 months) since the last change (removing tabs) 2) What is the status of the new_io library (Christian Henning was working on it I think). I think that this is the best hope for dealing with the IO issues I tend to have with GIL so far (it does not read RGBA jpegs either, it can not handle palettes, certain kinds of tiff compression, etc.) --John Index: png_io_private.hpp =================================================================== --- png_io_private.hpp (revision 48136) +++ png_io_private.hpp (working copy) @@ -291,6 +291,9 @@ default: io_error("png_reader_color_convert::apply(): unknown combination of color type and bit depth"); } break; + case PNG_COLOR_TYPE_PALETTE: + io_error("png_reader_color_convert::apply(): cannot read png images with a pallette (yet)"); + default: io_error("png_reader_color_convert::apply(): unknown color type"); } png_read_end(_png_ptr,NULL); Index: tiff_dynamic_io.hpp =================================================================== --- tiff_dynamic_io.hpp (revision 48136) +++ tiff_dynamic_io.hpp (working copy) @@ -56,13 +56,32 @@ class tiff_type_format_checker { int _bit_depth; int _color_type; + unsigned short _samples_per_pixel; public: - tiff_type_format_checker(int bit_depth_in,int color_type_in) : - _bit_depth(bit_depth_in),_color_type(color_type_in) {} + tiff_type_format_checker( int bit_depth_in + , int color_type_in + , unsigned short samples_per_pixel_in + ) + : _bit_depth(bit_depth_in) + , _color_type(color_type_in) + , _samples_per_pixel(samples_per_pixel_in) + {} template <typename Image> bool apply() { - return tiff_read_support<typename Image::view_t>::bit_depth==_bit_depth && - tiff_read_support<typename Image::view_t>::color_type==_color_type; + typedef tiff_read_support<typename Image::view_t> traits; + + int my_samples_per_pixel = size<typename Image::value_type>(); + + bool same_bit_depth = traits::bit_depth == _bit_depth; + bool same_color_type = traits::color_type == _color_type; + bool same_samples_per_pixel = my_samples_per_pixel == _samples_per_pixel; + + bool result = same_bit_depth && same_color_type; + + if (_samples_per_pixel) + result = result && same_samples_per_pixel; + + return result; } }; @@ -77,13 +96,17 @@ template <typename Images> void read_image(any_image<Images>& im) { - int width,height; - unsigned short bps,photometric; - TIFFGetField(_tp,TIFFTAG_IMAGEWIDTH,&width); - TIFFGetField(_tp,TIFFTAG_IMAGELENGTH,&height); - TIFFGetField(_tp,TIFFTAG_BITSPERSAMPLE,&bps); - TIFFGetField(_tp,TIFFTAG_PHOTOMETRIC,&photometric); - if (!construct_matched(im,tiff_type_format_checker(bps,photometric))) { + int width; + int height; + unsigned short bps=1; + unsigned short photometric = 1; + unsigned short samples_per_pixel = 0; + TIFFGetField(_tp, TIFFTAG_IMAGEWIDTH, &width); + TIFFGetField(_tp, TIFFTAG_IMAGELENGTH, &height); + TIFFGetField(_tp, TIFFTAG_BITSPERSAMPLE,&bps); + TIFFGetField(_tp, TIFFTAG_PHOTOMETRIC, &photometric); + TIFFGetField(_tp, TIFFTAG_SAMPLESPERPIXEL, &samples_per_pixel); + if (!construct_matched(im, tiff_type_format_checker(bps,photometric, samples_per_pixel))) { io_error("tiff_reader_dynamic::read_image(): no matching image type between those of the given any_image and that of the file"); } else { im.recreate(width,height); Index: tiff_io.hpp =================================================================== --- tiff_io.hpp (revision 48136) +++ tiff_io.hpp (working copy) @@ -1,6 +1,6 @@ /* Copyright 2005-2007 Adobe Systems Incorporated - + Use, modification and distribution are subject to the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) @@ -51,6 +51,12 @@ BOOST_STATIC_CONSTANT(int,color_type=PHOTOMETRIC_RGB); }; template <> +struct tiff_read_support_private<bits8,rgba_t> { + BOOST_STATIC_CONSTANT(bool,is_supported=true); + BOOST_STATIC_CONSTANT(int,bit_depth=8); + BOOST_STATIC_CONSTANT(int,color_type=PHOTOMETRIC_RGB); +}; +template <> struct tiff_read_support_private<bits16,gray_t> { BOOST_STATIC_CONSTANT(bool,is_supported=true); BOOST_STATIC_CONSTANT(int,bit_depth=16); @@ -94,6 +100,12 @@ BOOST_STATIC_CONSTANT(int,color_type=PHOTOMETRIC_RGB); }; template <> +struct tiff_write_support_private<bits8,rgba_t> { + BOOST_STATIC_CONSTANT(bool,is_supported=true); + BOOST_STATIC_CONSTANT(int,bit_depth=8); + BOOST_STATIC_CONSTANT(int,color_type=PHOTOMETRIC_RGB); +}; +template <> struct tiff_write_support_private<bits16,gray_t> { BOOST_STATIC_CONSTANT(bool,is_supported=true); BOOST_STATIC_CONSTANT(int,bit_depth=16); @@ -129,16 +141,18 @@ ~tiff_reader() { TIFFClose(_tp); } template <typename View> void apply(const View& view) { - unsigned short bps,photometric; + unsigned short bps,spp, photometric; point2<std::ptrdiff_t> dims=get_dimensions(); io_error_if(TIFFGetField(_tp,TIFFTAG_BITSPERSAMPLE,&bps)!=1); io_error_if(TIFFGetField(_tp,TIFFTAG_PHOTOMETRIC,&photometric)!=1); + io_error_if(TIFFGetField(_tp,TIFFTAG_SAMPLESPERPIXEL,&spp)!=1); io_error_if(dims!=view.dimensions(), "tiff_read_view: input view size does not match TIFF file size"); io_error_if(tiff_read_support_private<typename channel_type<View>::type, typename color_space_type<View>::type>::bit_depth!=bps || tiff_read_support_private<typename channel_type<View>::type, - typename color_space_type<View>::type>::color_type!=photometric, + typename color_space_type<View>::type>::color_type!=photometric || + mpl::size<typename color_space_type<View>::type>::value != spp, "tiff_read_view: input view type is incompatible with the image type"); std::size_t element_size=sizeof(pixel<typename channel_type<View>::type, layout<typename color_space_type<View>::type> >); @@ -166,14 +180,14 @@ }; // This code will be simplified... -template <typename CC> +template <typename CC> class tiff_reader_color_convert : public tiff_reader { private: CC _cc; public: - tiff_reader_color_convert(const char* filename) : + tiff_reader_color_convert(const char* filename) : tiff_reader(filename) {} - tiff_reader_color_convert(const char* filename,CC cc_in) : + tiff_reader_color_convert(const char* filename,CC cc_in) : tiff_reader(filename),_cc(cc_in) {} template <typename View> void apply(const View& view) { @@ -273,7 +287,7 @@ default: { // reads an image in incompatible format via TIFFReadRGBAImage rgba8_image_t rgbaImg(dims); - io_error_if(!TIFFReadRGBAImage(_tp, dims.x, dims.y, (uint32*)&gil::view(rgbaImg)(0,0), 0), + io_error_if(!TIFFReadRGBAImage(_tp, dims.x, dims.y, (uint32*)&gil::view(rgbaImg)(0,0), 0), "tiff_reader_color_convert::unsupported image format"); copy_and_convert_pixels(flipped_up_down_view(const_view(rgbaImg)), view, _cc); } @@ -353,7 +367,7 @@ /// \ingroup TIFF_IO /// \brief Loads the image specified by the given tiff image file name into the given view. /// Triggers a compile assert if the view color space and channel depth are not supported by the TIFF library or by the I/O extension. -/// Throws std::ios_base::failure if the file is not a valid TIFF file, or if its color space or channel depth are not +/// Throws std::ios_base::failure if the file is not a valid TIFF file, or if its color space or channel depth are not /// compatible with the ones specified by View, or if its dimensions don't match the ones of the view. template <typename View> inline void tiff_read_view(const char* filename,const View& view) { @@ -372,7 +386,7 @@ /// \ingroup TIFF_IO /// \brief Allocates a new image whose dimensions are determined by the given tiff image file, and loads the pixels into it. /// Triggers a compile assert if the image color space or channel depth are not supported by the TIFF library or by the I/O extension. -/// Throws std::ios_base::failure if the file is not a valid TIFF file, or if its color space or channel depth are not +/// Throws std::ios_base::failure if the file is not a valid TIFF file, or if its color space or channel depth are not /// compatible with the ones specified by Image template <typename Image> void tiff_read_image(const char* filename,Image& im) { /****************************************************************************** * __LICENCE_BEGIN__ * * __LICENCE_END__ *****************************************************************************/ ///@file ///@brief Test that RGBA images are detected by the TIFF reader. /// ///@author john.femiani(a)asu.edu /// /// #include <boost/test/unit_test.hpp> #include <boost/gil/gil_all.hpp> #include <boost/gil/extension/io/tiff_io.hpp> namespace gil = boost::gil; BOOST_AUTO_TEST_CASE(test_tiff_read_rgba8_image){ gil::rgba8_image_t rgb; ::boost::gil::tiff_read_image("images/rgba.tif", rgb); BOOST_CHECK_MESSAGE(rgb.width() == 86, "rgb.width() == 86 failed: Was " << rgb.width()); BOOST_CHECK_MESSAGE(rgb.height() == 64, "rgb.height() == 64 failed: Was " << rgb.width()); for (int y = 0; y < rgb.height(); ++y){ for (int x = 0; x < rgb.width(); ++x){ gil::rgba8_pixel_t pix = view(rgb)(x,y); BOOST_REQUIRE_MESSAGE(pix == gil::rgba8_pixel_t(128,128,128,255), "pix!=128,128,128,255 found pix=" << (int)pix[0] << "," << (int)pix[1] << "," << (int)pix[2] << "," << (int)pix[3] << " at x="<<x<<", y=" << y << "."); } } } BOOST_AUTO_TEST_CASE(test_tiff_read_rgb8_image_fails_on_rgba){ try { gil::rgb8_image_t rgb; ::boost::gil::tiff_read_image("images/rgba.tif", rgb); BOOST_FAIL("Reading an rgb image from an rgba tif should fail."); } catch (std::ios_base::failure& err ){ //Good, we should have an io error! } }

1 0

[boost.xpressive] RE for replacing problem
by Olaf Peter 14 Aug '08

14 Aug '08

Hi, my member function write() get called with string arguments like: Hello \n World \n Traceback ...\n NameError : name ... not defined \n etc. I want to add a prefix (a prompt '>>>' concete) so that the result will become: >>> Hello >>> World >>> Traceback .... >>> NameError: name ... not defined Yes, this comes from redirected python output. The simplest solution seems to use regex/xpressive: class redirector { const std::string m_prompt; const xpr::sregex m_re; const std::string m_re_fmt; public: redirector(const std::string& prompt = ">>> ") : m_prompt(prompt), m_re(xpr::sregex::compile("(\\n)!")), m_re_fmt(m_prompt + "\n") { } void write(const std::string& text) { std::cout << m_prompt << xpr::regex_replace(text, m_re, m_re_fmt); } ... }; where my regex won't work. What is the correct one since I can get a single '\n', a terminated '\n' or multiline strings separated by '\n'. Is this approach good for this problem? Anyway, I get a lot of warnings from constructor and write function, any ideas why? Thanks, Olaf

2 2

BGL: Trying to get my property bundle-using adjacency list to use a vector for its WeightMap.
by Geoff Hilton 14 Aug '08

14 Aug '08

Hi, I'm new to the boost and the BGL, and as the subject suggests, I'm trying to get my property bundle-using adjacency list to use a vector for its WeightMap. First off, the property bundles in question: template<size_t NumberOfBar> struct EdgeProperty { EdgeProperty(long double foo = 0):Foo(foo), Bar(NumberOfBar){} long double Foo; vector<long long> Bar; }; template<size_t NumberOfBar> struct VertexProperty { VertexProperty():Baz(NumberOfBar){} vector<pair<long long, long long> > Baz; }; The visitor: struct MyVisitor : public default_dijkstra_visitor { template <typename Vertex, typename Graph> void discover_vertex(Vertex u, const Graph& g) { cout << "discovered " << u << '\n'; } template <typename Edge, typename Graph> void tree_edge(Edge e, const Graph& g) { cout << "tree edge " << e << '\n'; } template <typename Edge, typename Graph> void examine_edge(Edge e, const Graph& g) { cout << "examining edge " << e << '\n'; } template <typename Vertex, typename Graph> void finish_vertex(Vertex u, const Graph& g) { cout << "finishing vertex " << u << endl; } }; The graph typedef: typedef adjacency_list< vecS, vecS, bidirectionalS, property<vertex_index_t, unsigned long long, VertexProperty<1> >, property<edge_index_t, unsigned long long, EdgeProperty<1> > > graph_t; Adding edges and vertices to the graph works without issue, as does assigning values to the properties, and navigating it, I was also able to get my test visitor to work.. using this code: int _tmain(int argc, _TCHAR* argv[]) { graph_t mygraph; //build graph //... //set up property accessors typedef EdgeProperty<1> EdgeProp; property_map<graph_t, long double EdgeProp::*>::type edge_foo_t = get(&EdgeProp::foo, mygraph); property_map<graph_t, vector<long long> EdgeProp::*>::type edge_bar_t = get(&EdgeProp::Bar, mygraph); property_map<graph_t, vertex_index_t>::type vertex_ind = get(vertex_index, mygraph); //dijkstra stuff size_t numberOfVertices = num_vertices(mygraph); std::vector<long double> distances(numberOfVertices, (numeric_limits<long double>::max)()); vector<vertex_descriptor> predecessors(numberOfVertices); MyVisitor vis; dijkstra_shortest_paths(mygraph, *vi, weight_map(edge_foo_t) .weight_map2(edge_bar_t) .distance_map( make_iterator_property_map(distances.begin(), vertex_ind) ) .predecessor_map( make_iterator_property_map(predecessors.begin(), vertex_ind) ) .visitor(vis) ); return 0; } However when I switch edge_bar_t and edge_foo_t within the weight_map/weight_map2 parentheses, I get this error (Visual Studio 2005) 'bool std::less<_Ty>::operator ()(const _Ty &,const _Ty &) const' : cannot convert parameter 1 from 'std::vector<_Ty>' to 'const D &' Of course that's normal because it's a vector. I figure I'm supposed to use make_iterator_property_map and somehow point it to &EdgeProp::Bar::begin() (or &EdgeProp::Bar::rbegin()) with a property_map<...> as I did with the others...but what I've tried so far hasn't worked. Any ideas? Thanks very much and best wishes, Geoff

1 1

Building boost 1.36
by Sean Farrow 13 Aug '08

13 Aug '08

Hi: I am trying to build boost 1.36, with the following command line: Bjam --toolset =msvc --build-type =complete. This gives me errors in bjam files. Any ideas what could be causing this error. Cheers Sean. __________ Information from ESET NOD32 Antivirus, version of virus signature database 3352 (20080813) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

2 2

bjam output
by Simon Pickles 13 Aug '08

13 Aug '08

Hi, I have finally got my head round boost::python and I'm loving it. I am on Ubuntu Hardy, stackless python 2.5, gcc 4.2.3. Two questions: 1) When using bjam to build libraries which expose C++ classes and functions to python, how can I use bjam to output the built libraries into a different folder to /bin/gcc-4.2.3/debug? 2) is this actually a debug library? if so, how do I create release versions? Many thanks Simon

3 4