|
I have some C++ code, and for some reason, for a couple of classes, they show up as boost::boost::boost::boost::boost::classname in the Visual Studio browser.
The classes themselves are not in the boost namespace.
There's no problem compiling the code...
Started by Eric H. on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
I installed boost 1.40 instead of 1.39, and the problem.
Arguments so these names can become quite complex.
|
|
Sau_timer::sau_timer(int secs, timerparam f) : strnd(io), t(io, boost::posix_time::seconds(secs)) { assert(secs > 0); this->f = f; //t.async_wait(boost::bind(&sau_timer::exec, this, _1)); t.async_wait(strnd.wrap(boost::bind(&sau_timer::exec, this...
Started by Motig on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
I mean:
t.async_wait(boost::bind(&sau_timer::exec, this, _1));
Did you try it and had:
sau_timer::sau_timer(int secs, timerparam f) : strnd(io), t(io, boost::posix_time::seconds(secs)) { assert(secs > 0); this....
But it is commented out.
|
|
How can I cast a boost::shared_array<char> to boost::shared_array<const char> ?
Started by Joakim Karlsson on
, 7 posts
by 7 people.
Answer Snippets (Read the full thread at stackoverflow):
Besides, are you sure you want a boost::shared_array<const char> and not a const boost::shared_array<char> ?
Practically, this works:
boost::shared_array<char> acz; boost::shared_array<const....
Shouldn't.
|
Ask your Facebook Friends
|
Hello, I've got this header (redone from a boost asio example):
#ifndef MSGSRV_H_ #define MSGSRV_H_ #include <asio.hpp> #include <boost/array.hpp> #include <boost/bind.hpp> #include <boost/shared_ptr.hpp> #include <boost/system...
Started by gotch4 on
, 5 posts
by 5 people.
Answer Snippets (Read the full thread at stackoverflow):
I don't have first-hand experience with boost::asio, but looking at the error message:
/usr/include/boost/bind/bind_template.hpp:61: instantiated from ‘typename boost::_bi::result_traits::type boost = boost::_mfi::mf....
|
|
What harm can come from defining BOOST_DISABLE_ABI_HEADERS when compiling boost?
From the boost file: boost_1_37_0\boost\config\user.hpp
// BOOST_DISABLE_ABI_HEADERS: Stops boost headers from including any // prefix/suffix headers that normally control...
Started by Brian R. Bondy on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
Here's what I could find on....
Without that, your application could not use the boost dlls installed by another statically to boost or if you can assure that your app only uses the boost dlls you compiled yourself it.
And compilers.
|
|
I would like to provide an extra boost::function to a async_write. I want the connections own HandleWrite function to be called first and then call the provided boost::function.
Member method of Connection that binds to asio async_write
void Connection...
Started by Joakim Karlsson on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
So I quickly hacked this to verify:
#include <boost/asio.hpp> #include <boost/bind.hpp> #include....
As I thought that the functors generated by boost::bind can take any number of arguments and simply ignore the extra ones.
|
|
On Page 175 Paragraph 1 of Effective C++ Meyers has this to say about generalized functors and binding:
I find what tr1::function lets you do so amazing, it makes me tingle all over. If you're not tingling , it may be because you're staring at the definition...
Started by Hassan Syed on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
What is "cool" about it is that, as with boost foreach and boost parameter , injects/extends syntax into C++ which.
Artifact, and because Lambda has its raison d'être , it exists in Boost.
|
|
It works just fine, for plain vanilla functions. The code below works just fine. It prints just what is should:
int __cdecl(int, char) 2 int,char
#include <boost/type_traits.hpp> #include <boost/function.hpp> #include <boost/typeof/std/...
Started by Jive Dadson on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
Boost Function Types would probably be the natural solution:
#include <boost/function_types/function_type.hpp> #include <boost/function_types/parameter_types.hpp> #include <boost/function_types/function_arity....
|
|
Hello all :)
I was using Boost 1.38, and I just upgraded to 1.39. Upgrading broke the following bit of code:
std::vector<std::wstring> consoleParser::loadStringsFromFile(const std::wstring &fileName) { std::vector<std::wstring> files; std:...
Started by BillyONeal on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
The latter link provides a patch that fixes....
Judging from this and this , it's indeed an issue with Boost 1.39.0 and VS2008.
Your compile failed because there's a new warning being emitted ( boost::detail::addr warnings as errors.
Settings.
|
|
As I recall BOOST_MPL_ASSERT was once preferred. Is this still true? Anyone know why?
Started by jwfearn on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
There was some talk a few months ago about deprecating BOOST_STATIC_ASSERT....
The messages from it are somewhat easier to see (and understand, if you use BOOST_MPL_ASSERT_MSG ).
BOOST_MPL_ASSERT is (still) generally considered better.
|
