- Boost - lists.boost.org

[python] warnings removal
by Vicente BOTET 27 Nov '10

27 Nov '10

Hi, with gcc-4.3.4 there is a warning * warning: type attributes ignored after type is already defined gcc.compile.c++ bin.v2/libs/python/build/gcc-4.3.4/release/threading-multi/numeric.o In file included from ./boost/python/object/make_instance.hpp:9, from ./boost/python/object/make_ptr_instance.hpp:8, from ./boost/python/to_python_indirect.hpp:11, from ./boost/python/converter/arg_to_python.hpp:10, from ./boost/python/call.hpp:15, from ./boost/python/object_core.hpp:14, from ./boost/python/object.hpp:9, from ./boost/python/tuple.hpp:10, from ./boost/python/numeric.hpp:10, from libs\python\src\numeric.cpp:6: ./boost/python/object/instance.hpp:14: warning: type attributes ignored after type is already defined This warning can be removed by adding a forward declaration file. See attached patch. * warning: deprecated conversion from string constant to â€˜char*â€™ ./boost/python/object/instance.hpp:14: warning: type attributes ignored after type is already defined libs\python\src\object\class.cpp: In function â€˜int boost::python::property_init(PyObject*, PyObject*, PyObject*)â€™: libs\python\src\object\class.cpp:79: warning: deprecated conversion from string constant to â€˜char*â€™ libs\python\src\object\class.cpp:79: warning: deprecated conversion from string constant to â€˜char*â€™ libs\python\src\object\class.cpp:79: warning: deprecated conversion from string constant to â€˜char*â€™ libs\python\src\object\class.cpp:79: warning: deprecated conversion from string constant to â€˜char*â€™ This warning can be removed with attached patch. Can these patches be include in trunk? Best, Vicente

2 1

[web] bad link for 1.45 release notes
by Vicente BOTET 27 Nov '10

27 Nov '10

Hi, The link in http://www.boost.org/community/review_schedule.html related to the Boost 1.45 Released point to the release notes of 1.44. Can this be corrected? Best, Vicente

2 1

[python] more warnings removal
by Vicente BOTET 27 Nov '10

27 Nov '10

Hi again, here there is other warning and the associated patches D:\boost\trunk\libs\python\src\converter\builtin_converters.cpp:369: warning: â€˜boost::python::converter::::py_unicode_as_string_unaryfuncâ€™ defined but not used Best, Vicente

1 0

[cygwin] warning "BOOST_CYGWIN" redefined
by Vicente BOTET 27 Nov '10

27 Nov '10

Hi, There is a warning in Boost.Config under CYGWIN that appears to much times as the config files is used a lot. gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.3.4/release/link-static/threading-m ulti/wave_config_constant.o In file included from ./boost/config.hpp:53, from ./boost/wave/wave_config.hpp:16, from libs\wave\src\wave_config_constant.cpp:20: ./boost/config/platform/cygwin.hpp:10:1: warning: "BOOST_CYGWIN" redefined In file included from ./boost/config.hpp:35, from ./boost/wave/wave_config.hpp:16, from libs\wave\src\wave_config_constant.cpp:20: ./boost/config/compiler/gcc.hpp:96:1: warning: this is the location of the previ ous definition John, I have attached a patch. for the trunk. Could it be include? Best, Vicente

2 1

[python] still compile error using pyhton 3.x
by Christopher Lux 27 Nov '10

27 Nov '10

Hi, since 1.44 boost python does not compile anymore using python 3.x (after a GSOC project it worked fine with python 3.1). I reported this after the 1.44 release and i thought someone had fixed it. This is really sad to see this great library not working anymore. These are the errors generated: compile-c-c++ e:\devel\_ext\boost_out_64\out\boost\bin.v2\libs\python\build\msvc-10.0\debug\address-model-64\threading-multi\object\function_doc_signature.obj function_doc_signature.cpp E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/detail/caller.hpp(55) : warning C4244: 'return' : conversion from 'Py_ssize_t' to 'unsigned int', possible loss of data libs\python\src\object\function_doc_signature.cpp(287) : warning C4244: 'initializing' : conversion from 'boost::python::ssize_t' to 'int', possible loss of data libs\python\src\object\function_doc_signature.cpp(294) : warning C4244: '=' : conversion from 'boost::python::ssize_t' to 'int', possible loss of data libs\python\src\object\function_doc_signature.cpp(303) : warning C4244: '=' : conversion from 'boost::python::ssize_t' to 'int', possible loss of data

4 4

[1.45.0] PDF build of documentation available
by John Maddock 26 Nov '10

26 Nov '10

The PDF build of the documentation for Boost-1.45 is now available for download from https://sourceforge.net/projects/boost/files/boost-docs/1.45.0/ Enjoy, John Maddock.

1 0

[interprocess] why not use boost/system/error_code?
by Christian Holmquist 26 Nov '10

26 Nov '10

Hi, Is there any reason to have an own error code wrapper in boost::interprocess/errors.hpp, instead of using boost::system::error_code? Cheers, Christian

3 3

[guidelines] why template errors suck
by Eric Niebler 26 Nov '10

26 Nov '10

This is borderline self-promotion and I fretted posting this. But we a community of advanced C++ library developers and I'd really like feedback about these issues. And they really do involve Boost library development. If we could reach agreement about these techniques, we might want to integrate them into Boost's coding guidelines. http://www.reddit.com/r/programming/comments/diddg/expressive_c_why_templat… Comments? -- Eric Niebler BoostPro Computing http://www.boostpro.com

24 136

Bug-fix volunteers: risks, downsides?
by Jim Bell 26 Nov '10

26 Nov '10

To round out the discussion... What risks or downsides would there be to recruiting a little legion of bug-fix volunteers and turning them loose on the tickets and/or regression matrix?

10 23

[1.44][build] Improving support for VC10 and Adding support for Intel C++ 12
by Jeff Benshetler 26 Nov '10

26 Nov '10

I'm working through updating msvc.jam to better support VC10, primarily so that intel-win.jam works more cleanly for Intel C++ 12. It looks like the last substantial revision to msvc.jam was for VC8, although it still works well for VC9 and VC10. The changes I've made work well; my next post is to Intel about "internal error: 0_1374", which seems to be a catch-all. My overall goal is to better support the new target architectures and optimization features available in VC10 and Intel C++ 12. I'm new here, so I wanted to make sure that 1) I'm not duplicating work; 2) I'm following the appropriate procedure. BTW, I posted to the Boost Build list a couple days ago and there has been no traffic at all. Any guidance is appreciated.

2 1