Nabble - Boost

Re: Help needed in fixing warnings

2009-11-10T10:33:11Z

On Tue, Nov 10, 2009 at 1:58 AM, John Maddock <john@...> wrote:
> Nod. I don't think anyone is suggesting that all of boost be warning free
> with all possible compilers, that just wouldn't be possible IMO.

It is possible. For me, the bottom line from this discussion is that
#pragma warning and #pragma GCC system_header are my best friends. :)

> But does
> that mean that we shouldn't try to do better with the most popular tools?

I think first we need to figure out what's the goal of removing
warnings: is it to impose higher warning level to developers, or to
provide warning-free user experience.

If it is the former, I find it inappropriate to cherrypick some
warnings *we* consider silly and tell the user, you know what, we're
not doing anything about these particular ones, gg. If I work at a
company that requires warning-free builds, one warning is one warning
too many.

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Official warnings policy?

2009-11-10T10:17:00Z

> C4512 fix looks good to me, but I also note some warnings C4244:
> 'argument' :
> conversion from 'const int' to 'const short', possible loss of data
>
> These could be quieted with carefully checked static_cast s.
>
> This checks and documents that the narrowing IS expected.

As long as it really is expected :-)

I haven't looked though, so I don't know anything about this case.

> In the jamfile you can suppress the C4535 calling _set_se_translator()
> requires
> /EHa with
>
> project : requirements ...
>
> adding
>
> <toolset>msvc:<asynch-exceptions>on # calling _set_se_translator()
> requires /EHa
>
> It would be better if Boost.Test did this?

Nod. Not sure if it can in this case, since Variant doesn't actually link
to the Boost.Test binaries.

> boost\boostsvn\boost\test\impl\execution_monitor.ipp(1161) : warning
> C4701:
> potentially uninitialized local variable 'old_crt_hook' used
>
> looks dodgy in Boost.Test too? Trak tickets?

I've already filed a patch against Boost.Test for this and other issues:
https://svn.boost.org/trac/boost/ticket/3598

John.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Official warnings policy?

2009-11-10T09:58:27Z

C4512 fix looks good to me, but I also note some warnings C4244: 'argument' :
conversion from 'const int' to 'const short', possible loss of data

These could be quieted with carefully checked static_cast s.

This checks and documents that the narrowing IS expected.

In the jamfile you can suppress the C4535 calling _set_se_translator() requires
/EHa with

project : requirements ...

adding

<toolset>msvc:<asynch-exceptions>on # calling _set_se_translator() requires /EHa

It would be better if Boost.Test did this?

boost\boostsvn\boost\test\impl\execution_monitor.ipp(1161) : warning C4701:
potentially uninitialized local variable 'old_crt_hook' used

looks dodgy in Boost.Test too? Trak tickets?

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal, UK LA8 8AB
+44 1539 561830, mobile +44 7714330204
pbristow@...

> -----Original Message-----
> From: boost-bounces@... [mailto:boost-bounces@...] On
Behalf Of

> Richard Webb
> Sent: Tuesday, November 10, 2009 3:52 PM
> To: boost@...
> Subject: Re: [boost] Official warnings policy?
>
>
> I've attached a patch for a bunch of Variant warnings from VC9 to
> https://svn.boost.org/trac/boost/ticket/1507, if anyone fancies taking a
> look at it.
>
> Thanks,
> Richard Webb

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Use of the * operator for matrix-matrix multiplication

2009-11-10T09:51:12Z

Hello,

I wonder why the uBlas library uses the function prod for the matrix-matrix and the matrix-vector multiplication.
I would have expected that the * operator is used for that purpose instead.

Greetings,
rolf

From forum: Boost - uBLAS

Re: Problem with PPC Darwin Nightly Tests

2009-11-10T09:22:44Z

K. Noel Belcourt wrote:
> I've attached the relevant part of the nightly test error we're having
> on PPC Tiger. It looks like an issue with feature.jam.

Sorry, this was my mistake. I made a change which started using the
patch version on the Xcode SDK detection. Which worked for iPhone
builds, but not regular OSX builds. I just checked in a quick fix. A
better, more flexible, fix will come along in the near future.

--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

From forum: Boost - Testing

Re: bjam + purify

2009-11-10T09:03:14Z

On Nov 9, 2009, at 10:33 PM, Vladimir Prus wrote:

> On Monday 09 November 2009 Anant Rao wrote:
>
>> Is there a way to build c++ code with bjam + purify on win, linux
>> or both?
>> If so, could you provide links to the info?
>> If not, is there any effort going on in that direction so I can
>> look forward to it one day?
>
> how is purify supposed to be used? The link I could find suggest
> that you just
> run purify on a normally-built binary, in which case things should
> work? If one
> should use "purify g++" to build binaries, instead, you can
> configure gcc as follows:
>
> using gcc : purify : "purify g++" ;
>
> in your user-config.jam, and then say:
>
> bjam toolset=gcc-purify
>
> Let me know if this helps,

Hi,

Here's a sampling of the changes we made to bring up Purify in
Boost.build. Basically we defined an instrument feature and defined
valgrind, purify, etc.. as valid instruments. Then we build with

bjam ... instrument=purify

Let me know if you want more details.

-- Noel

builtin.jam:# instrument built targets (usually instrument linked
executables)
builtin.jam:feature.feature instrument : none purify purecov quantify
valgrind cachegrind zerofault : propagated ;
builtin.jam:# diagnose and report error if instrument is an
incidental feature
builtin.jam:local tool = [ MATCH "^instrument=(.*)" : $(.argv) ] ;
builtin.jam: ECHO "Error: you can use more than one instrument if
you're not installing" ;
builtin.jam: ECHO " and found instrument=$(tool) which is
unsupported" ;
builtin.jam: ECHO " Remove the --installname option or use
only one instrument when installing" ;

cuda.jam:toolset.flags cuda.link CONFIG_COMMAND <instrument>purify/
<runtime-link>shared
cuda.jam:toolset.flags cuda.link OPTIONS <instrument>purify/<runtime-
link>shared
cuda.jam:toolset.flags cuda.link CONFIG_COMMAND <instrument>quantify/
<runtime-link>shared
cuda.jam:toolset.flags cuda.link OPTIONS <instrument>quantify/
<runtime-link>shared

gcc.jam:# get build directory for target instrument output
gcc.jam:toolset.flags gcc.link CONFIG_COMMAND <instrument>purify/
<runtime-link>shared
gcc.jam:toolset.flags gcc.link OPTIONS <instrument>purify/<runtime-
link>shared
gcc.jam:toolset.flags gcc.link CONFIG_COMMAND <instrument>purecov/
<runtime-link>shared
gcc.jam:toolset.flags gcc.link OPTIONS <instrument>purecov/<runtime-
link>shared
gcc.jam:toolset.flags gcc.link CONFIG_COMMAND <instrument>quantify/
<runtime-link>shared
gcc.jam:toolset.flags gcc.link OPTIONS <instrument>quantify/<runtime-
link>shared

sun.jam: flags sun.link OPTIONS <address-model>64/
<instrument>none : -m64 ;
sun.jam: flags sun.link OPTIONS <instrument>purify/<runtime-
link>shared/<address-model>64 : -m64 ;
sun.jam: flags sun.link OPTIONS <instrument>quantify/<runtime-
link>shared/<address-model>64 : -m64 ;
sun.jam: flags sun.link OPTIONS <instrument>purify/<runtime-
link>shared/<address-model>64 : -xarch=v9 ;
sun.jam: flags sun.link OPTIONS <instrument>quantify/<runtime-
link>shared/<address-model>64 : -xarch=v9 ;
sun.jam:# get build directory for target instrument output
sun.jam:flags sun.link CONFIG_COMMAND <instrument>purify/<runtime-
link>shared
sun.jam:flags sun.link CONFIG_COMMAND <instrument>quantify/<runtime-
link>shared

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

From forum: Boost - Build

Problem with PPC Darwin Nightly Tests

2009-11-10T08:59:43Z

Hi,

I've attached the relevant part of the nightly test error we're
having on PPC Tiger. It looks like an issue with feature.jam.

Thanks.

-- Noel

A boost/boost.css
A boost/CMakeLists.txt
U boost
Checked out revision 57528.
# Found patch file "/Users/kbelco/boost_tiger_ppc/patch_boost". Executing it.
# Preinstalled "/Users/kbelco/boost_tiger_ppc/bjam" is not found; building one...
# Found "bjam" source directory "/Users/kbelco/boost_tiger_ppc/tools_bjam"
# Building "bjam" (./build.sh darwin)...
###
### Using 'darwin' toolset.
###
rm -rf bootstrap
mkdir bootstrap
cc -o bootstrap/jam0 command.c compile.c debug.c expand.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c
./bootstrap/jam0 -f build.jam --toolset=darwin --toolset-root= clean
...found 1 target...
...updating 1 target...
...updated 1 target...
./bootstrap/jam0 -f build.jam --toolset=darwin --toolset-root=
...found 47 targets...
...updating 2 targets...
[MKDIR] bin.macosxppc
[COMPILE] bin.macosxppc/bjam
...updated 2 targets...
# Searching for "bjam" in "/Users/kbelco/boost_tiger_ppc/tools_bjam"...
# bjam succesfully built in "/Users/kbelco/boost_tiger_ppc/tools_bjam/bin.macosxppc/bjam" location
# Preinstalled "/Users/kbelco/boost_tiger_ppc/process_jam_log" is not found; building one...
# Found "process_jam_log" source directory "/Users/kbelco/boost_tiger_ppc/tools_regression/build"
# Building "process_jam_log" ("/Users/kbelco/boost_tiger_ppc/tools_bjam/bin.macosxppc/bjam" "-sBOOST_BUILD_PATH=/Users/kbelco/boost_tiger_ppc:/Users/kbelco/boost_tiger_ppc/tools_bb" "-sBOOST_ROOT=/Users/kbelco/boost_tiger_ppc/boost" "--boost=/Users/kbelco/boost_tiger_ppc/boost" "--boost-build=/Users/kbelco/boost_tiger_ppc/tools_bb" "--debug-configuration" process_jam_log -d2 -l300 darwin)...
notice: found boost-build.jam at /Users/kbelco/boost_tiger_ppc/boost-build.jam
notice: loading Boost.Build from /Users/kbelco/boost_tiger_ppc/tools_bb
notice: Searching /etc /Users/kbelco /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc/tools_bb/kernel /Users/kbelco/boost_tiger_ppc/tools_bb/util /Users/kbelco/boost_tiger_ppc/tools_bb/build /Users/kbelco/boost_tiger_ppc/tools_bb/tools /Users/kbelco/boost_tiger_ppc/tools_bb/contrib /Users/kbelco/boost_tiger_ppc/tools_bb/. for site-config configuration file site-config.jam .
notice: Loading site-config configuration file site-config.jam from /Users/kbelco/boost_tiger_ppc/tools_bb/site-config.jam .
notice: Searching /Users/kbelco /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc/tools_bb/kernel /Users/kbelco/boost_tiger_ppc/tools_bb/util /Users/kbelco/boost_tiger_ppc/tools_bb/build /Users/kbelco/boost_tiger_ppc/tools_bb/tools /Users/kbelco/boost_tiger_ppc/tools_bb/contrib /Users/kbelco/boost_tiger_ppc/tools_bb/. for user-config configuration file user-config.jam .
notice: Loading user-config configuration file user-config.jam from /Users/kbelco/boost_tiger_ppc/tools_bb/user-config.jam .
notice: [python-cfg] Configuring python...
notice: [python-cfg] user-specified version: "2.3"
notice: [python-cfg] user-specified cmd-or-prefix: "/usr/bin/python"
notice: [python-cfg] Checking interpreter command "/usr/bin/python"...
notice: [python-cfg] running command '"/usr/bin/python" -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1'
notice: [python-cfg] ...requested configuration matched!
notice: [python-cfg] Details of this Python configuration:
notice: [python-cfg] interpreter command: "/usr/bin/python"
notice: [python-cfg] include path: "/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3"
notice: [python-cfg] library path: "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/config" "/System/Library/Frameworks/Python.framework/Versions/2.3/lib"
notice: [python-cfg] framework directory is "/System/Library/Frameworks/Python.framework"
===============MPI Auto-configuration===============
Found recent LAM-MPI or Open MPI wrapper compiler: mpic++
MPI compilation flags: -D_REENTRANT -I/usr/local/include
MPI link flags: -Wl,-u,_munmap -Wl,-multiply_defined,suppress -L/usr/local/lib -lmpi_cxx -lmpi -lopen-rte -lopen-pal
MPI build features:
<define>_REENTRANT <include>/usr/local/include <library-path>/usr/local/lib <find-shared-library>mpi_cxx <find-shared-library>mpi <find-shared-library>open-rte <find-shared-library>open-pal <linkflags>-Wl,-u,_munmap <linkflags>-Wl,-multiply_defined,suppress
MPI launcher: mpirun -np
====================================================
notice: OSX version on this machine is 10.4.11
notice: will use '/usr/bin/g++' for darwin, condition <toolset>darwin-4.0.1
notice: using strip :: <toolset>darwin-4.0.1 :: /usr/bin/strip
notice: using archiver :: <toolset>darwin-4.0.1 :: /usr/bin/libtool
/Users/kbelco/boost_tiger_ppc/tools_bb/build/feature.jam:483: in feature.validate-value-string from module feature
error: "10.3.9" is not a known value of feature <macosx-version>
error: legal values: "10.6" "10.5" "10.4" "10.3" "10.2" "10.1" "iphone-3.2" "iphonesim-3.2" "iphone-3.1.2" "iphonesim-3.1.2" "iphone-3.1" "iphonesim-3.1" "iphone-3.0" "iphonesim-3.0" "iphone-2.2.1" "iphonesim-2.2.1" "iphone-2.2" "iphonesim-2.2" "iphone-2.1" "iphonesim-2.1" "iphone-2.0" "iphonesim-2.0" "iphone-1.x"
/Users/kbelco/boost_tiger_ppc/tools_bb/build/property.jam:276: in validate1 from module property
/Users/kbelco/boost_tiger_ppc/tools_bb/build/property.jam:301: in validate from module property
/Users/kbelco/boost_tiger_ppc/tools_bb/build/property.jam:310: in property.validate-property-sets from module property
/Users/kbelco/boost_tiger_ppc/tools_bb/build/toolset.jam:151: in flags from module toolset
/Users/kbelco/boost_tiger_ppc/tools_bb/tools/darwin.jam:262: in init-available-sdk-versions from module darwin
/Users/kbelco/boost_tiger_ppc/tools_bb/tools/darwin.jam:209: in darwin.init from module darwin
/Users/kbelco/boost_tiger_ppc/tools_bb/build/toolset.jam:38: in using from module toolset
/Users/kbelco/boost_tiger_ppc/tools_bb/user-config.jam:28: in modules.load from module user-config
/Users/kbelco/boost_tiger_ppc/tools_bb/build-system.jam:241: in load-config from module build-system
/Users/kbelco/boost_tiger_ppc/tools_bb/build-system.jam:383: in load-configuration-files from module build-system
/Users/kbelco/boost_tiger_ppc/tools_bb/build-system.jam:538: in load from module build-system
/Users/kbelco/boost_tiger_ppc/tools_bb/kernel/modules.jam:283: in import from module modules
/Users/kbelco/boost_tiger_ppc/tools_bb/kernel/bootstrap.jam:142: in boost-build from module
/Users/kbelco/boost_tiger_ppc/boost-build.jam:17: in module scope from module

# Searching for "process_jam_log" in "/Users/kbelco/boost_tiger_ppc/tools_regression/build"...
Traceback (most recent call last):
File "run.py", line 60, in ?
runner(root)
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 193, in __init__
self.main()
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 551, in main
getattr(self,action_m)()
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 508, in command_regression
self.command_setup()
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 300, in command_setup
self.build_if_needed(self.process_jam_log,self.pjl_toolset)
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 650, in build_if_needed
tool[ 'build_path' ] = self.tool_path( tool )
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 673, in tool_path
raise Exception( 'Cannot find "%s" in any of the following locations:\n%s' % (
Exception: Cannot find "process_jam_log" in any of the following locations:
/Users/kbelco/boost_tiger_ppc/process_jam_log
/Users/kbelco/boost_tiger_ppc/tools_regression/build
s863076:~/boost_tiger_ppc kbelco$

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Boost.build.txt (682 bytes) Download Attachment

From forum: Boost - Testing

Re: [gil] Committing some code changes

2009-11-10T08:57:47Z

AMDG

Christian Henning wrote:
> Hi there, I'm in the process to add some non-invasive code changes for
> boost::gil. Since this is my first time to commit changes to boost I
> would like to make sure I'm doing it right. The changes would be added
> to the trunk. Is that the right place?
>

Yes.

> I have done the obvious steps on my local machine. And besides adding
> comments when checking in my changes what other steps do I have to do?
>

After you commit you should watch the regression tests at
http://www.boost.org/development/tests/trunk/developer/summary.html

once the tests have cycled you can merge to /branches/release
as long as we aren't in the middle of a release.

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

[gil] Committing some code changes

2009-11-10T08:26:12Z

Hi there, I'm in the process to add some non-invasive code changes for
boost::gil. Since this is my first time to commit changes to boost I
would like to make sure I'm doing it right. The changes would be added
to the trunk. Is that the right place?

I have done the obvious steps on my local machine. And besides adding
comments when checking in my changes what other steps do I have to do?

Thanks,
Christian
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Jamfile to control MSVC compiler options /Za and /Ze

2009-11-10T08:13:19Z

Paul A. Bristow wrote:

> I have been taking my own medicine and trying to get Boost.math free of warnings
> with the /Za No MS extensions option.
>
> Mostly this is fine.
>
> project
> : requirements
> <toolset>msvc:<cxxflags>/Za # disable MS Extensions in Boost.Test.
> ...
>
> But a few tests require the extensions.
>
> I have tried to enable them for just one module thus:
>
> # pow test requires type_of that MS extensions.
> run pow_test.cpp ../../test/build//boost_test_exec_monitor
> : # command line
> : # input files
> : # requirements
> <toolset>msvc:<cxxflags>/Ze # Requires type_of which requires MS
> extensions.

Hi Paul,
could you try, instead of the above requirement, to add this:

-<toolset>msvc:<cxxflags>/Za

That's literal minus sign in front of requirement, and it should cancel out
the requirement for project.

Let me know if this helps.

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

boost::graph - Newbie question about vertex properties

2009-11-10T08:13:04Z

Hello dear mailing list members,

i'm new to this mailing list and hope i'm right here and that my english is not
too annoying.

I have to to some distance calculation and decided to use the
boost::graph-framework to do this as i have to develop a C++ application using
Visual C++ Express Edition 2008. I have to include some background details
information in the vertices and edges of my graph and chose to append such meta
info objects to the vertices and edges with the help of properties. I defined
the following types in the Header-Class:

[code]
struct vtx_ref_t {
typedef boost::vertex_property_tag kind;
};
struct edge_ref_t {
typedef boost::edge_property_tag kind;
};

// VtxMetaClass and EdgeMetaClass are some Classes containing some
// infos needed for calculation
typedef boost::property<vtx_ref_t, VtxMetaClass*> VtxProperty;
typedef boost::property<edge_ref_t, EdgeMetaClass*> EdgeProperty;
typedef boost::adjacency_list<boost::vecS, boost::vecS,
boost::directedS, VtxProperty, EdgeProperty> MyGraphType;

typedef boost::graph_traits<MyGraphType>::vertex_descriptor vertex_t;
typedef boost::graph_traits<MyGraphType>::edge_descriptor edge_t;
[/code]

In the Main-Method i tried to use the function boost::put to append such a meta
class object infoobj to a vertex (whose vertex descriptor vtx i only have) i
have created somewhere else where i cannot append the infoobject cause i don't
know at that time which one to append.

[code]
MyGraphType graph(100);
vertex_t vtx = boost::add_vertex(graph);
VtxMetaClass* infoobj;
...
boost::property_map<MyGraphType, vtx_ref_t>::type vtxref =
get(vtx_ref_t(), graph);
boost::put(vtxref, graph, vtx, infoobj);
[/code]

But i only get a compilation error telling me that:
1>e:\development\VC++\project\include\boost/pending/property.hpp(46) : error
C2039: 'kind': is no element of
'boost::vec_adj_list_vertex_property_map<Graph,GraphPtr,ValueType,Reference,Tag>'

What is wrong with that, i did what was suggested in the online manual ?

I know there's also the possibility to use boost::put with the index of the
vertex that has to be manipulated, but i don't know how to query the index from
the vertex_descriptor i have, perhaps you came across a way to do this yet ...

Perhaps you could help me with this problem ?
Thank you very much in anticipation,
Stephen

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: Official warnings policy?

2009-11-10T07:52:09Z

I've attached a patch for a bunch of Variant warnings from VC9 to
https://svn.boost.org/trac/boost/ticket/1507, if anyone fancies taking a look at it.

Thanks,
Richard Webb

From forum: Boost - Dev

Re: [test] Linking against boost_unit_test_framework causes double-deletion in std::ostringstream

2009-11-10T07:33:35Z

Roman Perepelitsa wrote:

> 2009/11/10 Alastair Rankine <arsptr@...>
>>Just curious if anyone else has seen this or anything like it? Platform
>>is Mac OS X 10.6.1, gcc 4.2.1, boost 1.40.0 installed from MacPorts,
>>compiling 64-bit (default).
I have crashes and "double deletions" in my unit tests, too.
I am running Linux, gcc 4.2.1, Boost 1.41.0-beta1;
(I have no crashes or double deletions with Boost 1.40.0.)

> As far as I remember, boost_unit_test_framework defines main function.
> Having two main functions in the same application might be what's causing
> your problems.
Definitely no two mains; 'my' main comes from a macro provided by
Boost.Test.

> Another possibility is that the library and the program are
> compiled with different standard libraries.
I have built both boost and my programs/tests myself, so I can rule the
"different standard library" thing out.

Best regards

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: Boost.Variant is not EqualityComparable

2009-11-10T07:13:11Z

Hi to all,

I've the same problem. I've created a union graph adaptor, that provides
a "union view" of two graphs; in that adaptor, the edge_descriptor is
defined like this:

typedef boost::variant<
WR1<typename graph_traits<Graph1>::edge_descriptor>,
WR2<typename graph_traits<Graph2>::edge_descriptor>
> edge_descriptor;

Now I would to use that graph to the Dijkstra's algorithm, that requires
that the edge_descriptor models the EqualityComparable concept:

http://www.sgi.com/tech/stl/EqualityComparable.html

But as we know, boost::variant doesn't support the inequality
expression. I've tried to add it from my code (I would avoid to modify
the boost lib), but it doesn't works. I've added the attached operator
after the union graph adaptor, but the compiler doesn't resolve the
function.

I'm using MSVS 2005. I don't know if it's my fault or of the compiler
lookup.

If I apply the Brook's patch, it works, but I would to avoid it.

Is this the right way to do?

Thanks,
Cosimo Calabrese.

Eric Friedman wrote:

> I think operator!= (and operator<=, operator>, operator>=) were left out for
> simplicity, but no good reason other than that.
>
> The main issue I considered at the time was that I felt variant should
> forward to the underlying operator. That is, it should call operator!=,
> rather than assume operator!= is equivalent to the negation of operator==.
>
> Maybe there's no need to be this pedantic though. Do others have an opinion?
>
> Eric
>
> On Mon, May 25, 2009 at 6:56 PM, Brook Milligan <brook@...>wrote:
>
>> I just ran into the case that Boost Variant does not satisfy the
>> EqualityComparable concept. While it provides operator==() and
>> operator<() (and therefore is LessThanComparable), it does not provide
>> operator!=(), which is required for the EqualityComparable concept.
>>
>> Is this by design or oversight? It seems reasonable to expect that a
>> Boost Variant model this concept, but perhaps I am missing something.
>>
>> In case it is by oversight, the following patch seems to provide the
>> missing operator.
>>
>> Cheers,
>> Brook
>>
>> --- boost/variant/variant.hpp.orig 2009-05-13 21:21:59.000000000 -0600
>> +++ boost/variant/variant.hpp 2009-05-25 19:21:40.000000000 -0600
>> @@ -1681,6 +1681,8 @@
>> return rhs.apply_visitor(visitor);
>> }
>>
>> + bool operator!=(const variant& rhs) const { return !(*this == rhs); }
>> +
>> bool operator<(const variant& rhs) const
>> {
>> //
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost
>>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>

/*
the type:

graph_traits<union_graph<Graph1, Graph2> >::edge_descriptor

is defined as:

typedef boost::variant< WR1<typename graph_traits<Graph1>::edge_descriptor>,
WR2<typename graph_traits<Graph2>::edge_descriptor> > edge_descriptor;
*/

namespace detail {
template <typename Graph1, typename Graph2>
inline bool operator!=( const typename graph_traits<union_graph<Graph1, Graph2> >::edge_descriptor& left,
const typename graph_traits<union_graph<Graph1, Graph2> >::edge_descriptor& right )
{
return !( left == right );
}
}

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Jamfile to control MSVC compiler options /Za and /Ze

2009-11-10T06:57:04Z

I have been taking my own medicine and trying to get Boost.math free of warnings
with the /Za No MS extensions option.

Mostly this is fine.

project
: requirements
<toolset>msvc:<cxxflags>/Za # disable MS Extensions in Boost.Test.
...

But a few tests *require* the extensions.

I have tried to enable them for just one module thus:

# pow test requires type_of that MS extensions.
run pow_test.cpp ../../test/build//boost_test_exec_monitor
: # command line
: # input files
: # requirements
<toolset>msvc:<cxxflags>/Ze # Requires type_of which requires MS
extensions.
: test_pow
;

but the compiler complains about deprecation (and most importantly, that later
options do not override, so you can't specify /Za and them /Ze.

compile-c-c++
..\..\..\bin.v2\libs\math\test\test_pow.test\msvc-9.0\debug\asynch-exceptions-on
\threading-multi\pow_test.obj

cl : Command line warning D9035 : option 'Ze' has been deprecated and will be
removed in a future release

cl : Command line error D8016 : '/Za' and '/Ze' command-line options are
incompatible

Can any jam experts suggest a way round this (short of leaving the default
enable extensions, and making an exception for all the vast majority of modules
that are OK with /Za - too tedious to be attractive? Splitting into two classes
of tests is also ugly.)

Thanks.

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal, UK LA8 8AB
+44 1539 561830, mobile +44 7714330204
pbristow@...

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: [BGL] Schultes and Sanders Contraction Hierarchies Routing

2009-11-10T05:40:05Z

Has anyone looked at supporting Drs Schultes and Sanders Contraction Hierarchies Routing using Boost Graph?

No. For some reason, good results in graph algorithms don't filter down to us too quickly :)

If Andrew, Jeremiah or others have time to look at some of the papers, I would be interested in your thoughts on supporting this or even knowing that BGL might be the wrong tool to implement this with.

I only have time to give the paper a very brief look this morning, but it seems like it might be feasible to reproduce this with the BGL. However, there are so many components to the technique, that it would require careful planning. For example, contraction may be difficult to implement. The vast majority of our use cases target graph construction and query. Fully dynamic graphs... well, they're supported, but maybe not as well as we'd like.

I would certainly be interested to see somebody try to put this together for the BGL. I think it might drive a lot of interesting requirements for the library, and identify areas that we could improve on.

Andrew Sutton
andrew.n.sutton@...

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: getting shape of numpy array

2009-11-10T05:35:13Z

Hello Nathan.

Find my answers below.

2009/11/10 Nathan Huesken <boost-python@...>:

> Hi,
>
> I am trying to interaface a numpy array using boost::python::numeric::array.
>
> void function(numeric::array& a)
> {
> tuple shape=extract<tuple>(a.getshape());
> double x;
> int i,j;
> for(i=0;i<shape[0];++i)
> for(j=0;j<shape[1];++j)
> x=extract<double>(a[make_tuple(i,j)]);
> }
>
> Now I had to add
> numeric::array::set_module_and_type("numpy", "ndarray");
>
> to the module, hope that was correct.
>
> When I call this function in python, I get:
> AttributeError: 'numpy.ndarray' object has no attribute 'getshape'

The error comes out because, actually, numpy.ndarray has no getshape method.

>
> What is the correct way to do it?
>

Within your function, declare

const tuple &shape = extract<tuple>(in.attr("shape"));

I suggest you to have a look also at my open source library (mds-utils):

http://code.google.com/p/mds-utils/

I've written some from/to Python converters that are able to convert a
Python sequence directly into a Boost uBLAS vector or matrix.
If you download the software, you can build the doxygen documentation
(follow the instructions) and you will find an example for each C++
class or function.

In other words, using my library, you could write your function as:

void function(const boost::numeric::ublas::matrix<double>& m) {
...
}

and export it to Python and pass, from Python, a Numpy 2D array.

Have a look at mds-utils and at its usage examples.

Bye,
Michele

> Thanks!
> Nathan
> --
> _______________________________________________
> Cplusplus-sig mailing list
> Cplusplus-sig@...
> http://mail.python.org/mailman/listinfo/cplusplus-sig
>

--
Michele De Stefano
http://www.linkedin.com/in/micdestefano
http://code.google.com/p/mds-utils
http://xoomer.virgilio.it/michele_de_stefano
_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@...
http://mail.python.org/mailman/listinfo/cplusplus-sig

From forum: Python - c++-sig

Re: [integer] long long warning

2009-11-10T05:25:45Z

>> Not yet, but it hits my stuff as well, so sometime I want to see it
>> fixed.
>> BTW I believe there are quite a few changes to Boost.Integer in Trunk
>> that
>> have never been merged to release as well, which adds extra complications
>> :-(
>
> They mainly look like new developments, and the test results aren't
> great so IMO we should probably just move them onto a branch and copy
> the files from the release branch. They can be merged back later if
> someone wants to deal with them.

I had a quick look, and it appears that:

* The test programs take too long to build (someone needs to split them up).
* There seems to be a problem with print_out_template in the
integer_test.cpp program that is causing many of the failures (only gcc it
seems will resolve the overload as intended).

If someone thinks they can fix these that would be really cool :-)

John.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Official warnings policy?

2009-11-10T05:15:11Z

Emil Dotchevski wrote:

> On Mon, Nov 9, 2009 at 11:25 AM, Stewart, Robert
> <Robert.Stewart@...> wrote:
> > Emil Dotchevski wrote:
>
> >> Alternatively, the reviewers could compile at lower warnings level.
> >> Most likely they wouldn't even need to do that, because they will
> >> simply build using the author scripts, which will likely produce a
> >> build without warnings.
>
> > Either is certainly possible, but if there are established
> > warning levels, it
> > is reasonable to expect that level or stricter.
>
> This assumes that a policy that requires warnings to be "fixed" is
> desirable or that it will lead to a better Boost (note that I'm not
> arguing against disabling warnings in Boost headers.)

I have made no such assumption. In every post, I have used the phrase, "established warning levels," and the like. We have none presently. We have no policy regarding warnings as yet.

In the quote above, I even phrased it as, "if there are established warning levels." There's no assumption in that.

_____
Rob Stewart robert.stewart@...
Software Engineer, Core Software using std::disclaimer;
Susquehanna International Group, LLP http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: [test] Linking against boost_unit_test_framework causes double-deletion in std::ostringstream

2009-11-10T04:48:49Z

2009/11/10 Alastair Rankine <arsptr@...>

#include <sstream>

int main()
{
std::ostringstream str;
str << "Help Me!";

return 0;
}

Here's what I'm doing:

% g++ -o streamtest_bad -ggdb -L/opt/local/lib -lboost_unit_test_framework-mt-d streamtest.cpp

As far as I remember, boost_unit_test_framework defines main function. Having two main functions in the same application might be what's causing your problems. Another possibility is that the library and the program are compiled with different standard libraries.

Roman Perepelitsa.

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

getting shape of numpy array

2009-11-10T04:45:34Z

Hi,

I am trying to interaface a numpy array using boost::python::numeric::array.

void function(numeric::array& a)
{
tuple shape=extract<tuple>(a.getshape());
double x;
int i,j;
for(i=0;i<shape[0];++i)
for(j=0;j<shape[1];++j)
x=extract<double>(a[make_tuple(i,j)]);
}

Now I had to add
numeric::array::set_module_and_type("numpy", "ndarray");

to the module, hope that was correct.

When I call this function in python, I get:
AttributeError: 'numpy.ndarray' object has no attribute 'getshape'

What is the correct way to do it?

Thanks!
Nathan
--
_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@...
http://mail.python.org/mailman/listinfo/cplusplus-sig

From forum: Python - c++-sig

Re: running a server "in background mode" ??

2009-11-10T04:29:57Z

>     boost::asio::io_service io_service;
>     tcp_server server(io_service);
>     io_service.run();

io_service::run() does not return until there's no work for io_service.
But you can run io_service in another thread:

new boost::thread(&asio::io_service::run, &io_service); // note that
io_service object can't be local here, as it must outlive the thread!
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: BGL - parallel/distributed

2009-11-10T04:24:02Z

To be even more precise, it exits the code in function MPI_Comm_dup of
mpi library. On linux I guess you have to have the mpi running, but I
don't know how it is on windows with mpich2.

Jeremiah Willcock wrote:

> On Mon, 9 Nov 2009, Ondrej Sluciak wrote:
>
>> Ok, I tried the simplest possible example, but just didn't figure out
>> where the problem is. I am on windows, mpich2 installed, all boost
>> libs correctly compiled with mpi, but if I do something like
>>
>> #include <boost/graph/use_mpi.hpp>
>> #include <boost/graph/distributed/selector.hpp>
>> #include <boost/graph/distributed/adjacency_list.hpp>
>> #include <boost/graph/distributed/mpi_process_group.hpp>
>>
>> void main(){
>> using namespace boost;
>> typedef
>> adjacency_list<vecS,distributedS<graph::distributed::mpi_process_group,
>> vecS>, directedS> Graph;
>>
>> Graph g(4);
>>
>> };
>>
>> I always get linking problems like:
>> Error 7 error LNK2019: unresolved external symbol "void __cdecl
>> boost::graph::distributed::synchronize(class
>> boost::graph::distributed::mpi_process_group const &)"
>> (?synchronize@distributed@graph@boost@@YAXABVmpi_process_group@123@@Z)
>> referenced in function "public: __thiscall
>> boost::adjacency_list<struct boost::vecS,struct
>> boost::distributedS<class
>> boost::graph::distributed::mpi_process_group,struct
>> boost::vecS,struct boost::defaultS>,struct boost::directedS,struct
>> boost::no_property,struct boost::no_property,struct
>> boost::no_property,struct boost::listS>::~adjacency_list<struct
>> boost::vecS,struct boost::distributedS<class
>> boost::graph::distributed::mpi_process_group,struct
>> boost::vecS,struct boost::defaultS>,struct boost::directedS,struct
>> boost::no_property,struct boost::no_property,struct
>> boost::no_property,struct boost::listS>(void)"
>> (??1?$adjacency_list@UvecS@boost@@U?$distributedS@Vmpi_process_group@distributed@graph@boost@@UvecS@4@UdefaultS@4@@2@UdirectedS@2@Uno_property@2@U52@U52@UlistS@2@@boost@@QAE@XZ)
>> boostTest2.obj
>>
>> I think I have included all the necessary libs (including mpi.lib
>> from mpich directory), so I still don't understand where is the
>> problem. Does anyone tried distributed graph class?
>
> Are you also including the graph_parallel library?
> Boost.Graph.Parallel is not header-only, unlike almost all of the
> sequential Boost.Graph library.
>
> -- Jeremiah Willcock
> _______________________________________________
> Boost-users mailing list
> Boost-users@...
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>
>

--
Dipl.-Ing. Ondrej Sluciak
Room CG-04-06
Vienna University of Technology, Austria
Institute of Communications and Radio-Frequency Engineering
Gusshausstrasse 25-29/389
http://www.nt.tuwien.ac.at

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

The difference operator: the rule lit("policeman") - "police" will always fail ?

2009-11-10T04:19:18Z

Hello, dear spirit devs!

i am curious if there's a way to parse "foobar" while not allowing "foo"? here's an explanation:

//cut here
struct keywords : qi::symbols<char> {
keywords(){
add
("if")
("else")
//...etc
}
} keywords_symbols;

rule<Iterator, std::string(), ascii::space> name;
name %= raw[
lexeme
[
((alpha | char_('_')) >> *(alnum | char_('_')))
- keywords_symbols
]
];
//cut here

This rule doesn't allow such inputs as "ifxxx", "else123".

According to the new docs about "The Difference operator, (a - b)":
Unlike classic Spirit, with Spirit2, the expression will always fail if the RHS is a successful match regardless if the RHS matches less characters. For example, the rule lit("policeman") - "police" will always fail to match. Spirit2 does not count the matching chars while parsing and there is no reliable and fast way to check if the LHS matches more than the RHS.

Could you be so kind to provide me with solutions for my task? Thank you guys!

From forum: spirit-general

Re: [Review] GGL review starts today, November 5th

2009-11-10T03:37:50Z

Hi Joachim,

> I am currently reading your docs and I think your design is *very* good.
>
Thanks, good to hear.

> I will take more time to investigate the lib and send a review at the end
> of the review period.
>
>
OK, perfect, looking forward to it.

Regards, Barend

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: running a server "in background mode" ??

2009-11-10T03:29:57Z

thanks very much for your support!!! i've understood that code, but however when i run it , i don't really see some difference, the server keeps in listening mode, blocking the execution of the rest of the code : i've added two simple line to print something on the console, and what i want is execute the server,that it keeps open in background but inmediatly execute too the printf code lines. main fuction would be :
.
.
.
.

int main()
{
try
{
    boost::asio::io_service io_service;
    tcp_server server(io_service);
    io_service.run();
    printf("Writting a line 1 \n");
    sleep(5);
    printf("Writting a line 2 \n");

}
catch (std::exception& e)
{
    std::cerr << e.what() << std::endl;
}

return 0;
}

2009/11/9 Maxime van Noppen <maxime@...>

pedro chaparro wrote:
> Hi, i need to use a server inside of other code application, i take the
> example from
> http://www.boost.org/doc/libs/1_40_0/doc/html/boost_asio/tutorial/tutdaytime2/src.html
> and it works but the server stay in listening mode and there is other
> code after that i'd like continue executing, is possible tu run the
> server let's say like in a background mode?

Hi,

You should look to how asynchronous operations work :

http://www.boost.org/doc/libs/1_40_0/doc/html/boost_asio/tutorial/tutdaytime3.html

--
Maxime
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

--
Ing Pedro Alonso Chaparro Valero
Ciudad Politecnica de la Innovación
iTEAM - Mobile Communications Group
Polytechnic University of Valencia
C\ Camino de Vera S/N, Edificio 8G
46022 Valencia, Spain

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: [Fusion] Views of Associative Sequences

2009-11-10T03:20:29Z

er schrieb:
> I wonder if I should wait for v1.41 (when : is there an estimate?) or if
> I can already remove joint_view.hpp from my current copy of boost and
> replace it with the new one : do you remember if the changes in
> joint_view standalone?

Unfortunately the changes in <boost/fusion/view/joint_view/*> are not
stand-alone, and I was too late to merge them into the 1.41 release branch.
I suggest you to work with a copy of the HEAD of the trunk.

-Christopher

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

[test] Linking against boost_unit_test_framework causes double-deletion in std::ostringstream

2009-11-10T02:50:20Z

Just curious if anyone else has seen this or anything like it? Platform
is Mac OS X 10.6.1, gcc 4.2.1, boost 1.40.0 installed from MacPorts,
compiling 64-bit (default).

Here's my test code:

#include <sstream>

int main()
{
std::ostringstream str;
str << "Help Me!";

return 0;
}

Here's what I'm doing:

% g++ -o streamtest_bad -ggdb -L/opt/local/lib
-lboost_unit_test_framework-mt-d streamtest.cpp
% ./streamtest_bad
streamtest_bad(63554) malloc: *** error for object 0x7fff7008a500:
pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
zsh: abort ./streamtest_bad
%

Works fine against other boost libraries, eg system:

% g++ -o streamtest_good -ggdb -L/opt/local/lib -lboost_system-mt-d
streamtest.cpp
% ./streamtest_good
%

Note that this seems to be a separate problem to that reported in
ticket 3432 (https://svn.boost.org/trac/boost/ticket/3432). At least, I
have verified that the framework::clear() function isn't being called
in the above code, which does tend to point the finger at a different
part of the library.

The backtrace is not particularly enlightening, but posted here for the
sake of completeness:

(gdb) bt
#0 0x00007fff87f92ff6 in __kill ()
#1 0x00007fff88034072 in abort ()
#2 0x00007fff87f4b095 in free ()
#3 0x0000000100005533 in __gnu_cxx::new_allocator<char>::deallocate
(this=0x7fff5fbff5df, __p=0x7fff7008a500 "") at new_allocator.h:97
#4 0x0000000100005578 in std::string::_Rep::_M_destroy
(this=0x7fff7008a500, __a=@0x7fff5fbff63f) at basic_string.tcc:431
#5 0x0000000100005939 in std::string::_Rep::_M_dispose
(this=0x7fff7008a500, __a=@0x7fff5fbff63f) at basic_string.h:238
#6 0x000000010000596a in std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::~basic_string
(this=0x7fff5fbff670) at basic_string.h:493
#7 0x000000010002ad55 in std::basic_stringbuf<char,
std::char_traits<char>, std::allocator<char> >::overflow
(this=0x7fff5fbff7f8, __c=72) at sstream.tcc:125
#8 0x0000000100029db0 in std::basic_streambuf<char,
std::char_traits<char> >::xsputn (this=0x7fff5fbff7f8, __s=0x100000e7e
"Help Me!", __n=8) at streambuf.tcc:102
#9 0x00007fff806e0ae4 in std::__ostream_write<char,
std::char_traits<char> > ()
#10 0x00007fff806deb98 in std::__ostream_insert<char,
std::char_traits<char> > ()
#11 0x00007fff806dec58 in std::operator<< <std::char_traits<char> > ()
#12 0x0000000100000d6b in main () at streamtest.cpp:6

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: [integer] long long warning

2009-11-10T02:41:26Z

On Tue, Nov 10, 2009 at 9:48 AM, John Maddock <john@...> wrote:
>
> Not yet, but it hits my stuff as well, so sometime I want to see it fixed.
> BTW I believe there are quite a few changes to Boost.Integer in Trunk that
> have never been merged to release as well, which adds extra complications
> :-(

They mainly look like new developments, and the test results aren't
great so IMO we should probably just move them onto a branch and copy
the files from the release branch. They can be merged back later if
someone wants to deal with them.

Daniel
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: [Review] GGL review starts today, November 5th

2009-11-10T02:36:22Z

2009/11/5 Hartmut Kaiser <hartmut.kaiser@...>:
>
> Hi all,
>
> The formal review of the Generic Geometry Library (GGL) starts today,
> November 5, 2009 and will finish November 15, 2009.

Hi Barend,

I am currently reading your docs and I think your design is *very* good.
I will take more time to investigate the lib and send a review at the end
of the review period.

Thanks to you, Bruno and Mateusz for this contribution.
Joachim
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

[msm] Version 2.0 available

2009-11-10T02:27:08Z

Dear Boosters,

I'm happy to announce the review-ready new version of Msm (2.0).
Msm is a framework which enables you to build a Finite State Machine
in a straightforward, descriptive and easy-to-use manner.
The generated code is optimized for speed and will force you to use
neither RTTI nor anything virtual.
Msm supports most of UML state machine features:
- state entry/exit
- transition actions/guards
- composite states
- history
- orthogonal regions
- terminate states
- deferred events
- explicit entry/fork
- entry/exit pseudostates
- anonymous transitions
- transition conflicts
and much more.

Msm v2.0 is a redesign of Msm v1.20 and offers a separation beetween
front- and back-ends. There is currently one backend and several
frontends:
- the same frontend as Msm v1.20
- a variation of this frontend based on functors for actions
- eUML, a boost::proto-based compile-time language allowing you to use
UML notations directly inside your code, thus making writing code from
a state machine diagram easier.

eUML also comes in with a functional programming library similar to
Boost.Phoenix, adapted to state machines.

I'll be happy for any comment.
You can find Msm v2.0 in:
- the vault (http://www.boostpro.com/vault/index.php?directory=Msm)
- the boost sandbox (http://svn.boost.org/svn/boost/sandbox/msm/)

The documentation can be found at libs/msm/doc/index.htm and the code
in the boost/msm subdirectory.

The 1.0 and 1.10 are now retired. To close up the 1.x path, I'll bring
a 1.21 with the latest bugfixes and then retire the 1.20 from the
vault.

Best regards,

Christophe
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: BGL - parallel/distributed

2009-11-10T02:17:51Z

You are right, that was what I was missing. Thank you. Anyway, no I can
compile it and run it, but the program always exits at the line Graph
g(4) with exit code 0x1. It quits in the inizialization of
mpi_process_group::impl::impl(std::size_t num_headers, std::size_t
buffer_sz, communicator_type parent_comm)
: comm(parent_comm, boost::mpi::comm_duplicate),
oob_reply_comm(parent_comm, boost::mpi::comm_duplicate),
allocated_tags(boost::mpi::environment::max_tag())

exactly in libs/mpi/src/communicator.cpp
communicator::communicator(const ...) on the line
BOOST_MPI_CHECK_RESULT(MPI_Comm_dup, (comm, &newcomm));

It doesn't crash or anything, just exits the code "normally" with exit
code 1.
Do you have any idea what is wrong?

Jeremiah Willcock wrote:

From forum: Boost - Users

Re: Help needed in fixing warnings

2009-11-10T02:17:48Z

> Would it be possible to get the warning output from the regression tests,
> at least for libs/{graph,property_map,graph_parallel}? I do not believe I
> have easy access to the compilers that are going to be used for warning
> checking.

Hmm, I can run graph and property_map locally, but I don't have MPI
configured/installed - I suspect it would be a lot easier for some with that
already available to run those!

The logs are quite large, so I'll mail them separately.

John.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Help needed in fixing warnings

2009-11-10T01:58:48Z

>> While not as easy for you as some yet undiscovered change to
>> noncopyable, can't you just use the MSVC pragma warning dance around
>> your classes to quiet that warning in each case?
>
> I could, and I might but....
>
> To my mind this is an invalid warning. The code in question is not
> incorrect
> and the boost::noncopyable provides the protection against the situation
> that the warning is designed to detect. So from my perspective the
> best would be to add /wd4511 and /wd4512 to the compiler switches.
>
> Of course that's not really a good solution because other code might
> not have the boost non_copyable protection. Ideally the compiler
> would be able detect that the copy/assigment functions can't be
> used in this case any way. Or maybe the compiler needs some sort
> of class attribute.

Nod. I think this is a common issue: the warning is entirely bogus in this
case, but in other contexts users may find it genuinely useful. The
question is whether we can silence the "noise" to a level that allows the
user to turn on a higher level of warnings and get useful output from their
code only. In this case yes, I believe we can.

> in the meantime...
>
> Of course I can conditionaly include pragma for this compiler.
> The problem is that you start have to doing for all compilers
> and they've all got their own set of quirks. This makes the
> code harder to read, understand and maintain. You HAVE
> to do it sometimes to work around bogus compiler errors
> but I'm sort of reluctant to embark upon this to work around
> bogus compiler warnings. This raises the question about how
> to handle the "warning" that such and such a function has been
> "deprecated" when it actually hasn't and of course those
> warnings which are just hints that sometimes have to be
> knowingly violated.
>
> Basically, once you start considering this - it sort of
> takes on a life of its own.

Nod. I don't think anyone is suggesting that all of boost be warning free
with all possible compilers, that just wouldn't be possible IMO. But does
that mean that we shouldn't try to do better with the most popular tools?

Not a rhetorical question, just feeling my way yours.... John.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: [integer] long long warning

2009-11-10T01:48:39Z

> if, in SVN trunk as of revision 57535, I go to libs/program_options/test
> and run:
>
> bjam warnings=all cxxflags=-Wextra
>
> I get a pile of warnings like this:
>
> ../../../boost/integer.hpp:145:24: warning: use of C99 long long integer
> constant
>
> These are actually only warnings that are now printed. Does anybody know
> what
> to do with them?

Not yet, but it hits my stuff as well, so sometime I want to see it fixed.
BTW I believe there are quite a few changes to Boost.Integer in Trunk that
have never been merged to release as well, which adds extra complications
:-(

Looking at the code in question, it appears the warning is from the
preprocessor phase as the line in question reads:

#if BOOST_HAS_XINT && (BOOST_UXINT_MAX > ULONG_MAX)

So we can't just declare constants-as-variables in one place to fix this as
we need values usable in preprocessor directives. Looks like we'll need
another #pragma GCC system_header, and as suggested elsewhere I'll try and
add a way to turn off those pragmas in Boost.Config.

HTH, John.

PS don't let warnings in dependencies stop you from declaring the library
"clean" on https://svn.boost.org/trac/boost/wiki/WarningFixes, it's
understood that dependencies may cause warnings, but they'll get fixed at
some point if we all work through the list.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev