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

Re: [Boost-users] [!! SPAM] [Boost.Wave] util::file_position<> and asserted !is_escaped_lit(..) requirement
by Hartmut Kaiser 13 Aug '11

13 Aug '11

> (Using namespace boost::wave here on.) > > It seems that util::file_position<> has an assertion that checks if a > given filename contains any following sequences: <\\>, <\"> or <\?> (using > util::debug::is_escaped_lit). > > I wonder why file_position<> does need to check this and if it's so > crucial why it's done using a mere BOOST_ASSERT? > > Now, here's comes the reason why I'm asking this: At least with MSVC9's > remote debugger (or some other lowlevel component; not really the > interesting part > here) translates all network shares on a remote computer to UNC-paths. > This is correct behaviour and actually a very neat feature. However, as > you might be already aware at this point this leads to the actual problem: > Any UNC-path triggers (consider <\\foo\path\file>) the assertion and > things go boom. > > It is not possible to easily work around this by refactoring user code > and/or input values as provided filenames are completed internally using > util::complete_path (after which <file> becomes <\\foo\path\file> etc. in > this case). > > I tried to disable this assertion (actually, there's two; one in the > constructor and one in the set_file member function) and didn't see any > strange behaviour. E.g. std::ifstream handling with UNC-paths in > iteration_context_policies::load_file_to_string::inner<> worked just fine, > as expected from a native STL. > > Goes without saying that I'm using the latest Boost version (1.47.0). I > would be very pleased if anyone could shed some light on this matter or > better still > - fix it permanently. Right, that's apparently a leftover from old boost.filesystem times, when it did not support UNC paths. I'll remove the checks asap. Regards Hartmut --------------- http://boost-spirit.com

1 0

[serialization] overloading load_construct_data: no accessible constructor at all
by Griffin Howlett 13 Aug '11

13 Aug '11

Hey, so I'm using the boost::serialization library, and I'm trying to override how a class is constructed, since it has no default constructor. This is demonstrated here<http://www.boost.org/doc/libs/1_47_0/libs/serialization/doc/serialization.h…>. To me it appears the function ONLY takes the `class* t` and then sets it to point to a newly constructed object. If I'm wrong, this is definitely the source of my error. However, the only way to construct my class is by using another classes `create()` function, meaning I need to stray from the code in the example (this is stated in the boost::serialization namespace): `::new(t)my_class(attribute);` I tried simply calling the create function and setting `t` equal to the returned pointer, but this doesn't seem to work because right after the `load_construct_data function`, and in the `serialization function`, the given `myClass&` is not the same as what I set 't' to. *How do I do whatever ::new(t) is doing so the object created using the create function follows through into the serialize/other functions?* [1]: http://www.boost.org/doc/libs/1_47_0/libs/serialization/doc/serialization.h…

1 0

JSON Property file reader compile problem
by Scott Smith 13 Aug '11

13 Aug '11

I'm trying to use the boost property tree to read a json file. I'm using 1.46 on gcc 4.6 (Fedora 15). I'm also running on Eclipse (Indigo) which is relevant for something I mention below. Here's the issue . I have a JSON file which has an array of parameters which looks something like: { "config": { "modules": [ { "name": "somename0", "param1": "someparam", "param2":"someotherparm" }, { "name": "somename1", "param1": "someparam", "param2":"someotherparm" }, { "name": "somename2", "param1": "someparam", "param2":"someotherparm" } ] } } So, I wrote the following code (Note that I can't use boost:FOR_EACH because of some bug in eclipse (#332278) which causes an error-or so I believe): ptree v = pt.get<ptree>("config.modules"); for (ptree::iterator it = v.begin() ; it != v.end ; ++it) { ptree module = ???; } The first two lines seem to compile fine. I'm assuming that what I get from v is the "root" ptree (the parent) for the various "modules" objects and that the iterator will walk through them. However, I've tried all sorts of things trying to get at the module data (e.g., it->second, (*it)->second, ...) and clearly I don't know what it is I need to tell the compiler I want. All I get are compile errors. The compiler is giving me no hints as to what I need to tell it. Can someone tell me what I'm missing here? Thanks Scott

2 1

(no subject)
by Hasanul Ferdaus 12 Aug '11

12 Aug '11

<p>living paycheck to paycheck wasnt working for me I told myself to stay positive without this id still be completely distraught!<br><a href="http://salanowyswiat.home.pl/PhilipBennett68.html">http://salanowyswiat.home.pl/PhilipBennett68.html</a> I waited so long for my time to shine<br></p>

1 0

[ASIO] Send data on a socket
by Claude 12 Aug '11

12 Aug '11

I created a socket with BOOST asio and I use it in a server process that accepts connections from "remote" client. It is possible from the process that created the socket, send data to the same socket simulating the arrival of data from a client process? -- View this message in context: http://boost.2283326.n4.nabble.com/ASIO-Send-data-on-a-socket-tp3738099p373… Sent from the Boost - Users mailing list archive at Nabble.com.

3 3

[Boost.Wave] util::file_position<> and asserted !is_escaped_lit(..) requirement
by Pekka Seppänen 12 Aug '11

12 Aug '11

Hello. (Using namespace boost::wave here on.) It seems that util::file_position<> has an assertion that checks if a given filename contains any following sequences: <\\>, <\"> or <\?> (using util::debug::is_escaped_lit). I wonder why file_position<> does need to check this and if it's so crucial why it's done using a mere BOOST_ASSERT? Now, here's comes the reason why I'm asking this: At least with MSVC9's remote debugger (or some other lowlevel component; not really the interesting part here) translates all network shares on a remote computer to UNC-paths. This is correct behaviour and actually a very neat feature. However, as you might be already aware at this point this leads to the actual problem: Any UNC-path triggers (consider <\\foo\path\file>) the assertion and things go boom. It is not possible to easily work around this by refactoring user code and/or input values as provided filenames are completed internally using util::complete_path (after which <file> becomes <\\foo\path\file> etc. in this case). I tried to disable this assertion (actually, there's two; one in the constructor and one in the set_file member function) and didn't see any strange behaviour. E.g. std::ifstream handling with UNC-paths in iteration_context_policies::load_file_to_string::inner<> worked just fine, as expected from a native STL. Goes without saying that I'm using the latest Boost version (1.47.0). I would be very pleased if anyone could shed some light on this matter or better still - fix it permanently. Br, Pekka

1 0

async_read_some() not found??
by Claude 12 Aug '11

12 Aug '11

I have this code (from async_read_until boost documentation): boost::asio::streambuf b; void handler(const boost::system::error_code& e, std::size_t size) { if (!e) { std::istream is(&b); std::string line; std::getline(is, line); // ... } } boost::asio::async_read_until(s, b, "\r\n", handler); But I obtain this error on Ubuntu 11.04 (boost 1.45.0): boost/asio/impl/read_until.hpp|388|*error: request for member ‘async_read_some’* in ‘((boost::asio::detail::read_until_delim_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp>*, std::allocator<char>, void (*)(const boost::system::error_code&, unsigned int)>*)this)->boost::asio::detail::read_until_delim_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp>*, std::allocator<char>, void (*)(const boost::system::error_code&, unsigned int)>::stream_’, which is of non-class type ‘boost::asio::basic_stream_socket<boost::asio::ip::tcp>*’ I Included in my project: libpthread libboost_system -- View this message in context: http://boost.2283326.n4.nabble.com/async-read-some-not-found-tp3732368p3732… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

[filesystem] misidentifies file type on Solaris x86 64-bit
by Will Mason 11 Aug '11

11 Aug '11

Hello, I'm using Boost 1.46.1 with filesystem v3. Code that I've been running successfully on Windows, Linux and FreeBSD started producing very mysterious results on Solaris. I boiled it down to this: boost::filesystem will not identify a directory as a directory. Here's a test program: #include <boost/filesystem.hpp> int main() { try { boost::filesystem::path d(boost::filesystem::absolute("dir")); if (boost::filesystem::exists(d)) { std::cout << d << " already exists" << std::endl; } else { boost::filesystem::create_directory(d); std::cout << d << " is " << (boost::filesystem::is_directory(d) ? "" : "not") << " a directory" << std::endl; } } catch (std::exception& e) { std::cout << "Exception: " << e.what() << std::endl; } return 0; } And here is a snippet of a terminal session compiling and running the program: $ CC -o fstest fstest.cpp -library=stlport4 -Iexternal/solaris/x86/64/suncc/5.11/include external/solaris/x86/64/suncc/5.11/lib/libboost_filesystem.a external/solaris/x86/64/suncc/5.11/lib/libboost_system.a $ ./fstest "/export/home/will/Projects/cap/dir" is not a directory $ file /export/home/will/Projects/cap/dir /export/home/will/Projects/cap/dir: directory $ Thanks for any help, Will

1 0

Boost Unit test on Eclipse
by Yong Qin 11 Aug '11

11 Aug '11

I have tried to use boost unit test on Eclipse CDT w/ MinGW and VC++. But I can not link to the static boost library: libboost_unit_test_framework-vc100-mt-1_47.lib. The code I used: #defineBOOST_TEST_MAIN #defineBOOST_TEST_MODULEMasterTestSuite #include<boost/test/unit_test.hpp> BOOST_AUTO_TEST_SUITE(FooTests) BOOST_AUTO_TEST_CASE(ctor_test1) { Fooa; BOOST_CHECK_EQUAL(a.name(),MY_PROJECT_NAMESPACE::Foo::DEF_NAME); } BOOST_AUTO_TEST_CASE(ctor_test2) { conststd::stringtheName("Blah"); Fooa(theName); BOOST_CHECK_EQUAL(a.name(),theName); } BOOST_AUTO_TEST_SUITE_END() What is wrong?

4 4

program_options: accepting NaNs for doubles
by Rhys Ulerich 11 Aug '11

11 Aug '11

Hi all, program_options does not accept NaN or Inf as valid double input. For example, the following sequence modifies the "Getting Started" first.cpp [1] to accept double input: cp $BOOST_SOURCE/libs/program_options/example/first.cpp . perl -pi -e 's/<int>/<double>/;' first.cpp LDFLAGS="-lboost_program_options" make first # ...or whatever The modified example indeed barfs on NaN or Inf input: $ ./first --compression=5.5 Compression level was set to 5.5. $ ./first --compression=Inf error: in option 'compression': invalid option value 'Inf' $ ./first --compression=NaN error: in option 'compression': invalid option value 'NaN' Two questions: 1) Does this count as a bug? 'std::cin >> foo' doesn't grok Inf or NaNs (on my system anyhow) but methods like strtod() do. Users providing explicit infinities or not-a-numbers as options parameters likely don't do so accidentally. This Inf/NaN behavior is not mentioned in the active tickets. 2) Can anyone suggest a workaround (shy of using string-based parameters and calling strtod myself)? Thanks, Rhys [1] http://www.boost.org/doc/libs/1_47_0/doc/html/program_options/tutorial.html…

2 2