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

Some questions about vertex removal in subgraph
by Nicholas Mario Wardhana 29 Mar '13

29 Mar '13

Hi all, In the last few days I have been implementing partial I/O for a subgraph by saving and loading a subgraph (although actually it is only partial if we see it from the parent graph's point of view). So far, by modifying some code in Boost, I managed to save a child graph to a file, and also load two subgraphs which share a vertex without having that vertex duplicated. However, in addition to save and load, I also need to clear (i.e. remove all nodes and edges from) a subgraph, and I found that remove_vertex is not implemented; only remove_edge is. I noticed that as of now (March 2013) there is no plan to implement it [1]. I cannot use Jeremiah's suggestion there (and also in [2]) to use filtered_graph, because I need to physically remove the nodes and edges from memory, so I am thinking to implement it myself. I have a few questions about this. 1) Jeremiah said that "In particular, local vertex descriptors in subgraphs are indices into an std::vector, and so removing a vertex would invalidate many other vertex descriptors." [1] Am I right to assume that this statement is about m_global_vertex, which is of std::vector<vertex_descriptor> type? 2) Removing a vertex from a regular graph involves calling g.m_vertices.erase(..) (adjacency_list.hpp, line 1951). I found that m_vertices is also of type std::vector. So why does vertex removal work for regular graph, but supposedly not for subgraph? I use Boost version 1.53.0, and my subgraph configuration is typedef adjacency_list<vecS, vecS, undirectedS, property<vertex_index_t, int, VertexProperty>, property<edge_index_t, int, EdgeProperty> > RegularGraph; typedef subgraph<RegularGraph> Subgraph; where VertexProperty and EdgeProperty are respectively bundled properties for vertex and edge. Thank you very much! Best regards, Nicholas Mario Wardhana References: [1] https://svn.boost.org/trac/boost/ticket/4752 [2] http://boost.2283326.n4.nabble.com/Can-t-link-subgraphs-because-remove-vert…

1 0

Re: [Boost-users] header-only libraries
by dib 27 Mar '13

27 Mar '13

> > >> I'd like to use the program_options library, but am reluctant to > >> require my users to build parts of Boost. Is there a strong > >> reason that this library cannot be header-only? > > You can build the necessary Boost CPP files as part of your own > build. > Asio (which is header-only) offers the possibility for "optional separate compilation" by including some ".../impl/src.hpp" in a source file and defining either "BOOST_ASIO_SEPARATE_COMPILATION" or "BOOST_ASIO_DYN_LINK", which very nicely lets the user choose which one suits best for his needs. Is there a reason why this isn't done for other libs like program_options, regex, etc., or has it (at least sometimes) just not been done because nobody wanted to do this extra-work? It is a very frequently asked question if/why not there is a header-only version, and although it is sometimes really not possible to make it header-only, most libs should work that way. Furthermore, in my experience specially commercial projects are reluctant to use libraries that have to be shipped with the own product, whereas it is no problem as long as they are "hidden" inside the binary.. Of course there are some disadvantages as shown in the discussion on stackoverflow, but giving the user a choice where possible should hugely increase acceptance and usage of those libraries. Greetings, dib PS: I just tried it with program_options and at least with my programs on linux it works fine, don't know how it is on other platforms or if I was just lucky: copy the src-files from libs/program_options/src to the include/boost/program_options/impl and do it "the asio-way", including the source files in a separate .cpp in my projects.. works fine and no linking is required any more.

3 4

header-only libraries
by ilya shlyakhter 26 Mar '13

26 Mar '13

Dear Boost experts, I'd like to use the program_options library, but am reluctant to require my users to build parts of Boost. Is there a strong reason that this library cannot be header-only? Or perhaps, it's possible to create a header-only version of this library? I have the same question for regex. Thanks, ilya

3 2

[MSM] "favor_compile_time" policy disables "kleene" events. (Bug?)
by Deniz Bahadir 25 Mar '13

25 Mar '13

Hi everyone, Hi Christophe, While trying to speedup compilation of my MSM/eUML-based state machine, I seem to have found a bug. I added the "favor_compile_time" policy to the type-definition of my state-machine as the documentation suggests. I did not use the macro "BOOST_MSM_BACK_GENERATE_PROCESS_EVENT" because I do not have any sub-statemachines. This did speed up compilation, however obviously by changing my transition-table: All "kleene"-events in my transition-table are ignored, when defining the state-machine with the "favor_compile_time" policy. Can anyone confirm this or am I using it wrong? (Was this policy supposed to work with eUML in the first place?) Thanks, Deniz PS: I am using GCC 4.7.2 with Boost 1.53.

3 6

Broken Links?
by Hei Chan 25 Mar '13

25 Mar '13

Hi, On http://www.boost.org/doc/libs/1_53_0/libs/pool/doc/html/boost_pool/pool/poo…, all the graphs there seem broken. Anyone fixing it? Thanks in advance. Cheers, Hei

2 1

[boost::Statechart] posting a "serial timeout" event
by Andre de Jong 25 Mar '13

25 Mar '13

I've been using boost's asynchronous statechart to write a program. In this program I communicate with another device using an asynchronous serial port. I have a state that waits for a confirmation from the device over the serial port and then posts a "confirmation received" event. This works well but, I would also like to implement a "timeout" event. In previous programs I had been using switch case statements for my state machines where I had code that could be run each time the loop was run. This meant I could run code and check if I should change state due to something timing out. Like this: while(1){ switch (state){ case 0:{ sendMessage(); state = 1; sendTime = boost::chrono::steady_clock::now(); } break; case 1:{ if (isConfirmationReceived()){ // do something state = 2; } else if (boost::chrono::steady_clock::now() > start + boost::chrono::duration<double>(WAIT_LENGTH)){ //do something state = 3; } } break; // etc etc } } How would I implement something like this using boost::StateChart? Or, should i be thinking about this a completely different way?

1 0

Re: [Boost-users] Broken Links?
by Boost_mailinglist＠gmx.de 25 Mar '13

25 Mar '13

Hello, you can see the directory listing of the pictures under http://www.boost.org/doc/libs/1_53_0/libs/pool/doc/images/ -----Ursprüngliche Nachricht----- Gesendet: Montag, 25 März 2013 um 06:32:27 Uhr Von: "Hei Chan" <structurechart(a)yahoo.com> An: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org> Betreff: [Boost-users] Broken Links? Hi, On�http://www.boost.org/doc/libs/1_53_0/libs/pool/doc/html/boost_pool/pool/…, all the graphs there seem broken. Anyone fixing it? Thanks in advance. Cheers, Hei _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

bad reloc address when compiling with mingw
by Leonardo Sá 24 Mar '13

24 Mar '13

Hi all, I have been trying to create an .exe that links to several boost libraries (date-time, python, etc.) using MinGW, cross compiling for windows on linux. I compiled boost using mingw without problems. When linking the exe, I am receiving the following error: CMakeFiles/fp_core_test.dir/objects.a(MockEnvironment.cpp.obj):MockEnvironment.cpp:(.text+0x381): undefined reference to `fp_core::Window::init(int, int, boost::shared_ptr<fp_core::Renderer>)' /usr/bin/i686-w64-mingw32-ld: CMakeFiles/fp_core_test.dir/objects.a(MockEnvironment.cpp.obj): bad reloc address 0x8 in section `.text$_ZN5boost6detail15sp_counted_baseC2Ev[boost::detail::sp_counted_base::sp_counted_base()] I have no idea what "bad reloc address" means. Googling wasn't much help. Anyone can give me a pointer in the right direction? Thanks!

1 0

newbie problem with Program Option string value
by Neil Sutton 24 Mar '13

24 Mar '13

I am having problems getting a program option to work. The option should enable a user to enter a location when they select the '--location' option. so, if you type --location canada, the code should store the supplied string - canada and pass it on to the program. This is a typical program option with nothing special. But I cannot seem to get it to work! Please look at this: ---------------------------------------------------- std::string place_option; // a global variable po::options_description general("General options"); general.add_options() ("location", po::value<std::string>(), "location of your home"); // there are other non string options po::variables_map vm; po::store(po::parse_command_line(ac,av, general),vm); po::notify(vm); if(vm.count("help")) { std::cout << general << "\n"; return 0; } if(vm.count("version, v")) { std::cout << "version aplha\n"; } if(vm.count("location")) { place_option = vm["location"].as<std::string>(); // should pass the string value entered at command line to std::string place. } If i run my program with eg 'myprogram --location disney' I get: terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct NULL not valid Aborted ------------------------------ Now I have tried a few variations of the code. The examples show where an int value is supplied and retrieved. I cannot work out how to do - what should be very trivial. I simply want to recover the value associated with 'location' i.e a std::string entered at the command line. I then want to pass that value on to my program to do something with it. I do not understand the error. Can someone kindly show me the correct syntax to accomplish this please? Kind regards.

3 2

[iostreams] mapped_file path issue
by Alexandre 24 Mar '13

24 Mar '13

Hello, After reading through all the documentation and examples I could read, I still can't get the following piece of code to work . I assume that when you pass a new_file_size and a path to the mapped_file_params class , it will then open the file at the location desired when I call the constructor of mapped_file with the mapped_file_params object in parameter. But the only thing it does is to create a file with a weird name , like "%F8/134" in the project working directory, not where I told it to. Maybe I'm wrong and one should create file before specifying it to the mapped_file? After reading the doc, I was under the assumption that it created a new file when you fill in the new_file_size param. and specifies the filename. Anyone experienced this before? Any advice on how to resolve this? Here's the code: boost::iostreams::mapped_file_params param(filename); // filename is a std::string with the correct path param.flags = boost::iostreams::mapped_file::mapmode::readwrite; param.new_file_size = sizeNeeded; // sizeNeeded is the size of the data param.length = sizeNeeded; boost::iostreams::mapped_file fileMap(param); // at this point the file is created … Thanks for your time, Alexandre

1 0