December 2010 - Boost-users - lists.preview.boost.org

[DateTime] overflow in posix_time::microseconds
by gast128 08 Dec '10

08 Dec '10

Hello all, we encountered an overflow in posix_time::microseconds: //about 40 years (1970-2010) const __int64 n = 1267195987000000; boost::posix_time::microseconds td(n); //overflow The overflow is easy explainable since date_time::subsecond_duration first multiplies it causing the overflow and then divides by 1000000. There are already multiple posts spended on this, but I saw no definitive answer. Can someone help? Alternatively we could work around it by first divide the hour part out of it (which makes the number smaller) before adding to a ptime, but preferably we would like this to see solved in the library itself.

1 1

Re: [Boost-users] mpi non-blocking communication
by Hicham Mouline 08 Dec '10

08 Dec '10

> (1) You must initialize MPI with MPI_Init_thread() instead of >MPI_Init(). The boost::mpi::communicator ctor uses MPI_Init(), so you >must run the initialization yourself and *then* create the >communicator object. For instance:: > MPI_Init_thread(&argc, &argv, MPI_THREAD_SERIALIZED) > // ... > mpi::communicator world; Riccardo, I have the following code in my main: int main(int argc, char* argv[]) { boost::mpi::environment env(argc, argv); const int mpi_thread_support = MPI::Init_thread(argc, argv, MPI_THREAD_SERIALIZED ); if (mpi_thread_support != MPI_THREAD_SERIALIZED) { std::cerr<< "MPI implementation does not support threads" <<std::endl; return 1; } boost::mpi::communicator world; ... } This prints an error however: Calling MPI_Init or MPI_Init_thread twice is erroneous. How does 1 avoid that the mpi::communicator constructor calling MPI_INIT twice? Perhaps it's the environment constructor that calls MPI_INIT? rds,

2 5

error when compiling boost 1.45
by Sean Farrow 08 Dec '10

08 Dec '10

Hi: I'[m trying to compile boost 1.45, with zlib/bzip2 support in the io streams library. My command line is: bjam toolset=msvc --stagedir=stage/vc/v10/32-bit -sZLIB_SOURCE="c:\progra~1\zlib" -sBZIP2_SOURCE="c:\progra~1\bzip2" --build-type=complete >boost.txt I get the following warning: LINK : fatal error LNK1181: cannot open input file 'boost_zlib.lib' This command line worked for compiling 1.44. Anyone got any ideas? Cheers Sean.

1 0

Re: [Boost-users] Code stopped compile after migrating 1.42->1.45 (worked around)
by Pavel Pervov 08 Dec '10

08 Dec '10

I've worked it around with the specialisation boost::lambda::bind<int> for now and filed a ticket #4962 (https://svn.boost.org/trac/boost/ticket/4962) WBR, Pavel. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

1 0

Code stopped compile after migrating 1.42->1.45
by Pavel Pervov 07 Dec '10

07 Dec '10

I'm compiling my codebase with Microsoft Visual C++ 8/9 (Visual Studio 2005/2008) Here is an example code which I've crafted from what I have in my codebase: //------- code start -------------------------------- #include <algorithm> #include <map> #include <string> #include <iostream> #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> typedef std::map<int, int> MyMap; std::ostream& operator << (std::ostream& outs, const MyMap& a) { std::for_each(a.begin(), a.end(), outs << boost::lambda::bind(&A::value_type::second, boost::lambda::_1) << "\n"); return outs; } int main() { MyMap a; std::cout << a; } //------- code end --------------------------------- This code stopped compiling after I've migrated from boost version 1.42 to version 1.45. Any ideas would be appreciated. Regards, Pavel --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

2 1

[Fusion] Flatten a sequence of sequences
by Clinton Mead 07 Dec '10

07 Dec '10

Hi All Lets say I have something like the following: make_vector(1, make_vector('b', 3, make_vector(4, 5.5), "six"), 7, 8) I want to produce an function f such that f(make_vector(1, make_vector('b', 3, make_vector(4, 5.5), "six"), 7, 8)) -> [1,'b',3,4,5.5,"six",7,8] i.e. a flattened version of the sequence. I don't mind if this is a view of the original sequence or an actual vector. I don't mind a solution in C++0x if it can compile on GCC 4.5.1. Thanks

3 2

[interprocess]/[thread] - named_recursive_mutex spurious wake using scoped_lock
by Daniel Biagini 07 Dec '10

07 Dec '10

I'm running boost 1.43 on linux and seeing an issue where the scoped_lock<named_recursive_mutex> timed lock is returning immediately when another thread holds the lock. The lock is being stored in shared memory Am I doing something wrong? The code in question is the azLog function below, (I included some other relevant snips as well). thanks! Dan #define LOCK_WAIT_TIME 5; //seconds static named_recursive_mutex *globalLock = create_logger_lock(); static named_recursive_mutex *create_logger_lock () { named_recursive_mutex *ptr = NULL; if (globalLock) { return(globalLock); } deadlock_count = 0; lock_timeout = LOCK_WAIT_TIME; try { ptr = new named_recursive_mutex(open_or_create, (getShareName() + GLOBAL_LOCK).c_str()); } catch (const interprocess_exception &ie) { cerr << "FATAL: Couldn't initialize the logging subsytem, IE err:" << ie.what() << endl; throw; } catch (const std::exception &se) { cerr << "FATAL: Couldn't initialize the logging subsytem, std err:" << se.what() << endl; throw; } return(ptr); } void azLog(AZ_LOG_SEVERITY sev, AZ_LOG_COMPONENT comp, const string& log_str) { ptime to = second_clock::local_time() + seconds(lock_timeout); scoped_lock<named_recursive_mutex> lock(*globalLock, to); while(!lock.owns() && (second_clock::local_time() < to)) { cerr << pthread_self() << ": SPURIOUS WAKE!!" << to_simple_string(second_clock::local_time()) << " <=:=> " << to_simple_string(to) << endl; lock.timed_lock(to); } .....

1 0

[BGL] vertex, edge, and face properties of graph?
by Anders Wallin 07 Dec '10

07 Dec '10

Hi All, I'm implementing a half-edge data structure(*) based on adjacency_list. I'm storing vertex and edge properties as bundled properties (classes VertProps and EdgeProps), and can read/write them conveniently with e.g.: graph[vertexDescriptor].vertProp_a = 2 and x = graph[edgeDescriptor].edgeProp_b etc. I also need to keep track of the faces of the planar graph, and I'm wondering if there's a built-in way of doing this that would allow me to read/write face-properties via the same syntax: graph[faceDescriptor].faceProperty Could I derive my half-edge-class from adjacency_list, store and update a property-map for face-data, and provide a new overload for operator[] that takes a faceDescriptor type? or is there a better way? any examples available? thanks, AW (*) see e.g. http://www.holmes3d.net/graphics/dcel/

2 1

Re: [Boost-users] Code stopped compile after migrating 1.42->1.45
by Pavel Pervov 07 Dec '10

07 Dec '10

Small correction to the code: //------- code start -------------------------------- #include <algorithm> #include <map> #include <string> #include <iostream> #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> typedef std::map<int, int> MyMap; std::ostream& operator << (std::ostream& outs, const MyMap& a) { std::for_each(a.begin(), a.end(), outs << boost::lambda::bind(&MyMap::value_type::second, boost::lambda::_1) << "\n"); return outs; } int main() { MyMap a; std::cout << a; } //------- code end --------------------------------- Pavel --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

2 1

BOOST Filesystem file_size problem
by Claude 07 Dec '10

07 Dec '10

Hi! I have a problem with file_size () If I try to use file_size () like this: MyFileName string ("myFile"); file_size (path (MyFileName)); [...] Undefined reference to `boost:: filesystem2:: detail:: file_size_api (std:: basic_string <char, std:: char_traits <char>, std:: allocator <char>> const &) '[...] What is wrong? -- View this message in context: http://boost.2283326.n4.nabble.com/BOOST-Filesystem-file-size-problem-tp307… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2