- Boost-users - lists.boost.org

ASIO / IO Completion Ports (Windows)
by asif saeed 02 Mar '11

02 Mar '11

Hi, I wonder if ASIO on Windows also implements IO Completion ports. I think this is called Proactor, right? I would be thankful if you point me to the right direction. Also, any links/examples of using ASIO with Boost::Thread (or TR1) would be very helpful. I am a newbie on ASIO & Boost Thread. Sincerely / Asif

2 1

Re: [Boost-users] [GIL] gray pixel iterator in generic algorithm
by Robert Lupton the Good 02 Mar '11

02 Mar '11

> With this, the unit test for my gray opening function with an unscaled float image now compiles and works fine. Does this mean that you have some clean way to handle gil images that don't automatically scale into [0,1]? If so, can we have it pushed into the next boost release? I have a clunky version of this that I'm not proud of, but I certainly need. I'm an astronomer, and the values in my images (unsigned short, int, float) are directly related to the number of photons detected so scaling is a real problem. R

2 1

[xint] Boost.XInt formal review
by Vladimir Prus 02 Mar '11

02 Mar '11

Boosters, the formal review of the Boost.XInt library, by Chad Nelson, starts now and will run through March 11. The documentation for the current version is available at: http://www.oakcircle.com/xint_docs/ The source code is available via Subversion at: http://svn.boost.org/svn/boost/sandbox/xint or can be downloaded at: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=xint.z… Here are the important points: 1. All comments are appreciated. Even if you don't have the time for in-depth study of everything, comments on parts of the library are welcome. In particular, if you are already using logging in your applications and have specialized requirements, you might want to directly check how the proposed library handles them. 2. The reviews and all comments should be submitted to the developers list, boost(a)lists.boost.org and the email should have "[xint]" prefix in the subject to make sure it's not missed. The deadline for reviews is 23:59, March 11, PST, or 2:59, March 12, EST, or 7:59 March 12, UK time, 10:59, March 12 MSK 3. Please explicitly state in your review whether the library should be accepted. 4. The general review checklist is provided below: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Thanks, Volodya -- Vladimir Prus Mentor Graphics +7 (812) 677-68-40

2 1

[Review] Phoenix V3: Mini-review ends March 2nd
by Hartmut Kaiser 02 Mar '11

02 Mar '11

This is just a friendly reminder that the mini-review of Phoenix V3 (written and submitted by Thomas Heller) ends tomorrow, March 2nd 2011. If you are planning to submit a review, please do so asap. If you need more time for your review, please get in direct contact with me. Regards Hartmut Review Manager --------------- http://boost-spirit.com

1 0

Boost.Thread: timed_join, interruption/cancellation and c++0x
by Daniel Neuberger 01 Mar '11

01 Mar '11

Am I understanding correctly that there's no plan to support timed_join and interruption/cancellation in c++0x. If so, will Boost.Thread continue to support them? Also, will Boost.Thread be adding support for variadic templates sometime soon? In short we want to use threads with variadic templates, but need support for timed_join and interruption points. Thanks, - Daniel

1 0

boost::ptime on the wire....
by david.weber＠l-3com.com 01 Mar '11

01 Mar '11

I've got a case, where I need to transmit a timestamp across the wire, in a cross-platform manner. My first choice was boost::ptime, but I cannot seem to find a way to serialize a timestamp in a nice compact manner (i.e.: Two UINT64's, or four, or whatever). This is actually pretty important, as I need to define the ICD between the sender and recipient. Am I just overlooking something slick? Thanks --dw

2 1

[python] intercepting uncaught exceptions
by Gennadiy Rozental 01 Mar '11

01 Mar '11

Hi, I am using Boost.Python quite extensively (even stretching it to the limit in some cases). Now I cave this problem: Is there any way to intercept uncaught exception in embedded Python code? I need to add some information to an exception/traceback in this case. I have full control over environment before embedded code is executed. I thought I'll be able to use sys.excepthook, but it does not seem to be invoked. Alternatively I'd can live if I can somehow retrieve the context of failed call (global/local dict?) in boost::python::error_already_set handler. Please advise, Gennadiy

3 5

[MSM] test if state machine is in a given state / const get_state
by Jan Vogelgesang 01 Mar '11

01 Mar '11

Hello all, i am working with the Boost 1.45 Meta State Machine, using both orthogonal regions and submachines. Overall, i am very happy with this library. But i am looking for a nice way to check if a state machine (e.g. instance mAvail of class AvailFSM) is in a given state, for example i would like to write something like this: assert(isInState(mAvail, AvailFSM::UpstreamAvailable())); I didn't find something like "isInState" provided by the MSM library, so i came up with the following implementation: template <class FSM, class StateType> bool isInState(const FSM& p, const StateType& s) { int stateId = boost::msm::back::get_state_id<typename FSM::stt,StateType>::value; for (int i=0; i < FSM::nr_regions::value; ++i) { if(p.current_state()[i] == stateId) { return true; } } return false; } This works well for simple state machines and orthogonal regions, but not for submachines. Does any one knows a way to extend the above code to work with submachines? Lets say the state "AvailFSM::UpstreamAvailable" from above is in fact a submachine, having the state "Primary" amongst others. It would be nice to have the following working: assert(isInState(mAvail, AvailFSM::UpstreamAvailable::Primary())); Currently i am using the following workaround: assert(isInState(mAvail, AvailFSM::UpstreamAvailable())); assert(isInState(mAvail.get_state<AvailFSM::UpstreamAvailable&>(), AvailFSM::UpstreamAvailable::Primary())); I consider this solution ugly not only because of its lengthiness, but also because "get_state" isn't a const function. Unfortunately i'am not deep enough into the template magic to tell if a const implementation of "get_state" is possible. Can anyone help me out ? So, to sum up, i have two questions: 1) How to implement something like "isInState" that even works on submachines, if possible ? 2) Is a const version of "get_state" possible ? And how? best regards, jan

1 0

boost::asio from C++ Forms App in VS 2010
by Alan Vella 01 Mar '11

01 Mar '11

Hi all, I'm trying to port a C++ project from gcc (on MinGW) to Visual Studio 2010 inside a Visual C++ Windows Forms application. The code was originally written on a Windows XP 32-bit machine. Now it is being ported into a Windows 7 32-bit machine. This project uses quite a few boost libraries, including the boost::asio library. When I try to compile the code in VS2010 I get the following errors: 1> Please define _WIN32_WINNT or _WIN32_WINDOWS appropriately. For example: 1> - add -D_WIN32_WINNT=0x0501 to the compiler command line; or 1> - add _WIN32_WINNT=0x0501 to your project's Preprocessor Definitions. 1> Assuming _WIN32_WINNT=0x0501 (i.e. Windows XP target). 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/impl/win_thread.ipp(52): error C2664: 'QueueUserAPC' : cannot convert parameter 1 from 'void (__stdcall *)(ULONG_PTR)' to 'PAPCFUNC' 1> Address of a function yields __clrcall calling convention in /clr:pure and /clr:safe; consider using __clrcall in target type 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/impl/win_thread.ipp(82): error C2664: '_beginthreadex' : cannot convert parameter 3 from 'unsigned int (__stdcall *)(void *)' to 'unsigned int (__stdcall *)(void *)' 1> Address of a function yields __clrcall calling convention in /clr:pure and /clr:safe; consider using __clrcall in target type 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/win_thread.hpp(31): error C3641: 'boost::asio::detail::win_thread_function' : invalid calling convention '__stdcall ' for function compiled with /clr:pure or /clr:safe 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/win_thread.hpp(36): error C3641: 'boost::asio::detail::apc_function' : invalid calling convention '__stdcall ' for function compiled with /clr:pure or /clr:safe 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/win_fenced_block.hpp(35): error C3862: 'boost::asio::detail::win_fenced_block::win_fenced_block': cannot compile an unmanaged function with /clr:pure or /clr:safe 1> Inline native assembly not supported in managed code 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/win_fenced_block.hpp(35): error C3645: 'boost::asio::detail::win_fenced_block::win_fenced_block' : __clrcall cannot be used on functions compiled to native code 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/win_fenced_block.hpp(54): error C3862: 'boost::asio::detail::win_fenced_block::~win_fenced_block': cannot compile an unmanaged function with /clr:pure or /clr:safe 1> Inline native assembly not supported in managed code 1>C:\Program Files\boost\boost_1_44\boost/asio/detail/win_fenced_block.hpp(54): error C3645: 'boost::asio::detail::win_fenced_block::~win_fenced_block' : __clrcall cannot be used on functions compiled to native code 1> 1>Build FAILED. Any help would be much appreciated. Cheers, Alan Vella. _______________________________________________________ Unlimited Disk, Data Transfer, PHP/MySQL Domain Hosting http://www.doteasy.com

8 10

Boost.Unordered: custom hasher
by gast128 01 Mar '11

01 Mar '11

Hello all, for using the unordered_set with a user defined class one can define a custom hasher. There seems to be the following options: - overide boost::hash_value - write ur own custom hash functor Both options have then an external hash function. I was more thinking about using a member function as hasher (e.g. like GetHashCode). A supporting class would be then: template <typename T, typename RetType, RetType (T::*pmf)() const> struct unary_function_mf : std::unary_function<T, RetType> { RetType operator()(const T& r) const { return (r.*pmf)(); } }; which makes specifying an unordered_set easier: boost::unordered_set<Person, unary_function_mf<Person, size_t, &Person::GetHashCode> > uset2; My questions: 1) is this correct c++ 2) does something similar exist in Boost (Boost.Function and Bind doesn't seem to support his) 3) is there an advantage of using a free function over functor? The free function has at least one advantage, that it also works with the std::pair hasher.

1 0