- Boost - lists.preview.boost.org

[fsm review] Terminal emulator example
by Phil Endecott 19 Aug '08

19 Aug '08

Dear All, Here's another FSM example which I hope is a bit less trivial than the last one. It's for the escape sequence handling in a terminal emulator. If you're curious you can see the real code here: http://svn.anyterm.org/anyterm/trunk/common/Terminal.cc The terminal emulator has to understand: - Normal characters like 'A' that write themselves on the screen at the current cursor position. - Normal control characters like tab, carriage return etc. A peculiar feature is that these characters can occur within escape sequences, where they have their normal effect. - Escape sequences, which consist of ESC followed by one character (normally a letter) and have effects like clearing the screen. - "CSI sequences", which perform more complex operations that may require parameters (e.g. scroll lines N to M up). They have the form ESC [ n1 ; n2 ; n3 ; ... X where the final letter X determines the operation and the number of numeric parameters is variable. So the state machine needs to track whether it is in an escape sequence, in a CSI sequence, or in "normal operation". The transitions are as follows: Current state | Condition | Next state ------------------------------------------------ Normal | ESC | ESC ESC | end of sequence | Normal ESC | [ | CSI ESC | char 26 | Normal CSI | end of sequence | Normal CSI | char 26 | Normal Character 26 explicitly abandons any escape sequence that is in progress. A terminal emulator should behave sensibly when it receives invalid input. One reasonable behaviour on receiving an invalid character is to ignore the preceding incomplete input and to treat the new character as if it had been received in normal mode; or, we could ignore the preceding incomplete input AND the new character and switch to normal mode. The following transitions do something along those lines: Normal | char 26 | Normal ESC | ESC | ESC ESC | invalid sequence | Normal CSI | ESC | ESC CSI | invalid sequence | Normal One thing that we don't want to do is to throw an exception when we get invalid input. My (stripped-down) ad-hoc implementation of this follows: class Terminal { screen_t screen; // basically a 2D array, with some features // for efficient scrolling int cursor_col, cursor_row; int params[MAX_PARAMS]; int nparams; enum state_t { normal, esc, csi }; state_t state; Terminal(): cursor_col(0), cursor_row(0), state(normal) {} void carriage_return() { cursor_col = 0; } void cursor_line_up() { cursor_row--; } void csi_CUU() { cursor_row -= params[0]; } // Lots more functions like those omitted. void write_normal_char(char c) { if (cursor_col>=cols) { cursor_col = 0; cursor_line_down(); } screen(cursor_row,cursor_col) = c; cursor_col++; } void process_char(char c) { // Control chars like tab, newline etc. work even inside // escape sequences: if (c <= 31) { switch (c) { .... case 13: carriage_return(); break; .... case 26: // This code abandons any escape sequence that is in progress state = normal; break; case 27: // Escape state = esc; break; .... } } else { switch (state) { case normal: write_normal_char(c); break; case esc: switch (c) { .... case 'M': cursor_line_up(); state=normal; break; .... case '[': state=csi; nparams=0; break; default: state=normal; break; } break; case csi: if (isdigit(c)) { if (nparams==0) { nparams=1; params[0]=0; } params[nparams-1] = params[nparams-1]*10 + (c-'0'); } else if (c==';') { if (nparams>=MAX_PARAMS) { return; } nparams++; params[nparams-1] = 0; } else { switch (c) { .... case 'A': csi_CUU(); break; .... } state = normal; } } } } }; OK, so let's try to implement that with the proposed library. As before, I haven't tried to compile any of this code: struct Normal; struct Esc; struct CSI; typedef mpl::vector<Normal,Esc,CSI>::type StateList; struct Common { screen_t screen; // BTW, how can I access this from outside? int cursor_col, cursor_row; void carriage_return() { cursor_col = 0; } void handle_control_chars(char c) { switch (c) { .... case 13: carriage_return(); break; .... case 26: // This code abandons any escape sequence that is in progress this->switch_to<Normal>(); break; case 27: // Escape this->switch_to<Esc>(); break; .... } } }; template <typename StateT> struct TermState: fsm::state<StateT,StateList>, virtual Common { // I think I need some using declarations here. Or do they have to be in each of // the derived classes? } struct Normal: TermState<Normal> { void write_normal_char(char c) { if (cursor_col>=cols) { cursor_col = 0; cursor_line_down(); } screen(cursor_row,cursor_col) = c; cursor_col++; } void on_process(const char& c) { if (c<=31) { handle_control_char(c); } else { write_normal_char(c); } } }; struct Esc: TermState<Esc> { void cursor_line_up() { cursor_row--; } void on_process(const char& c) { if (c<=31) { handle_control_char(c); } else { switch (c) { .... case 'M': cursor_line_up(); switch_to<Normal>(); break; .... case '[': switch_to<CSI>(); break; default: switch_to<Normal>(); break; } } } }; struct CSI: TermState<CSI> { int params[MAX_PARAMS]; int nparams; void on_enter() { nparams=0; // doing this here is nice } void csi_CUU() { cursor_row -= params[0]; } void on_process(const char& c) { if (c<=31) { handle_control_char(c); } else { if (isdigit(c)) { if (nparams==0) { nparams=1; params[0]=0; } params[nparams-1] = params[nparams-1]*10 + (c-'0'); } else if (c==';') { if (nparams>=MAX_PARAMS) { return; } nparams++; params[nparams-1] = 0; } else { switch (c) { .... case 'A': csi_CUU(); break; .... } switch_to<Normal>(); } } } }; My view is that the ad-hoc version of the code is sufficiently readable and efficient for my needs, and that the Boost.FSM version does not improve on it. What do other people think? Am I choosing bad examples? If so, please can someone post an example that does demonstrate the library's advantages? (Maybe off-topic, but if any Spirit or Expressive experts would like to show how their libraries would deal with this problem I'd be interested to see that.) Regards, Phil.

2 3

FSM Review Announcement
by Martin Vuille 19 Aug '08

19 Aug '08

The formal review for Andrey Semashev's Finite State Machines (FSM) library is scheduled for August 11th to 20th. Quoting from the documentation: "The main goals of the library are: * Simplicity. It should be very simple to create state machine using this library. * Performance. The state machine infrastructure should not be very time and memory-consuming in order to be applicable in more use cases. * Extensibility. A developer may want to add more states to the existing state machine, and this addition should be relatively safe since it shouldn't interfere with the existing states. The developer should also be able to specify additional transitions and events for the machine with minimum modifications to the existing code." "The following compilers are known to have problems or most likely will have ones: * Microsoft Visual C++ 6.0 and 7.0. Most probably will fail to compile due to lack of partial template specialization support. * Borland C++ Builder 5.5.1 (free version). Fails to compile due to lack of partial template specialization and in-class using declarations support. Some other minor problems also have been noticed. Newer versions of the compiler have not been tested. * OpenWatcom 1.5. Fails to compile due to problems with Boost.MPL code. Newer versions of the compiler have not been tested. * SunPro C++ Compiler 5.5 for Solaris (SPARC). Most likely will show problems with function overload resolution. Newer versions of the compiler have not been tested." The current submission is available from the sandbox vault at http://tinyurl.com/yjozfn (or http://www.boostpro.com/vault/index.php?action=downloadfile&filename=FSM.zip &directory=&PHPSESSID=48493076c1ea60ae316f7b60f15b9ed1, if you prefer.) MV

15 47

[exception] doc error
by Daryle Walker 19 Aug '08

19 Aug '08

[This is based of an unrelated post that mentioned a file in the 1.36 release branch. I just looked and the trunk also has it.] <http://svn.boost.org/svn/boost/trunk/libs/exception/doc/ enable_current_exception.html>, as of revision 47496, has an error in its beginning. It wants T to be a user-defined type so it can derived publicly from it. However, user-defined type doesn't mean class type; it also includes enums, which can't be derived from. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1

Can multi-index do this?
by Daryle Walker 19 Aug '08

19 Aug '08

Is it possible for Boost.Multi-index, or anything else in Boost, to make a container that is generally random-access (like vector or deque) but efficiently allows removals anywhere (like list)? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

4 6

[Boost.IOStreams] Error with c++ builder 2007
by Sean Farrow 18 Aug '08

18 Aug '08

Hi: When compiling the boost trunk, I get an error that the compiler can't cast 'const mapped_file_sink' to 'const mapped_file &' the line is 474 In libs\iostreams\src\mapped_file.cpp and reads: : mapped_file(static_cast<const mapped_file&>(other)) Anyone got any clue what is happening here? Chers Sean. __________ Information from ESET NOD32 Antivirus, version of virus signature database 3365 (20080818) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

1 0

Can't use CLR with boost so...
by Jamie Justice 18 Aug '08

18 Aug '08

I need to convert a char array to a byte array of ASCII encoded characters to send over a TCP connection, but I can't use the CLR(and therefore the System namespace) with boost. Does anyone have a solution to this? Thanks, Jamie

2 1

[filesystem] major problem with 1.36 on OS X
by Matthias Schabel 18 Aug '08

18 Aug '08

Attempting to compile and link the following code with a default build of 1.36 on OS X 10.5.4 (Intel) // test.cpp #include <fstream> #include <iostream> #include <string> #include <vector> //#include <boost/system/error_code.hpp> //#include <boost/system/system_error.hpp> #include <boost/filesystem/operations.hpp> #include <boost/filesystem/path.hpp> int main (int argc, char * const argv[]) { boost::filesystem::create_directory("blah"); return 0; } results in a linker error, even though the method in question is defined inline in <boost/system/error_code.hpp> : Undefined symbols: "boost::system::error_code::message() const", referenced from: boost::system::system_error::what() constin ccyMBSNr.o ld: symbol(s) not found collect2: ld returned 1 exit status This is reproducible both from a clean XCode 3.0 project and from the command line : gcc test.cpp -I/usr/local/include -I .. -L/usr/local/lib - lboost_filesystem-xgcc40-mt -lboost_system-xgcc40-mt -lstdc++ Uncommenting the explicit includes doesn't help, either. This is a weird one... Matthias

2 4

Re: [boost] Boost 1.36.0 release notice
by Beman Dawes 18 Aug '08

18 Aug '08

Joe Gottman wrote: > Beman Dawes wrote: >> Boost 1.36.0 has been released and is available from SourceForge. See >> http://sourceforge.net/projects/boost/ >> >> This release include four new libraries: >> > I just downloaded the version 1.36 and the release history is > completely blank. Grrr... One of my highest priority tasks for the next release is going to be to get a system in place that will automatically scan a release snapshot for the presence of certain files, and optionally verify size, date, and other properties. Thanks for the heads up. --Beman

7 17

Identification library preliminary version
by joel falcou 18 Aug '08

18 Aug '08

Hello all, I've uploaded a preliminary version of my type identification library into the vault (identification-v.01.zip) It's the current implementation of my type debugging facility that provides a simple function and class to build at run-time a human readable string containing the name of its type arguments. Identification supports a simple way to register user-defined types into itself. Samples and documentation are provided. It has been tested on g++ v4+ (both linux and windows) and on MSVC 2008 with equal success. Test on other platform and compiler are welcome as well as general comments on the interface or implementation choices. Thanks in advance.

2 4

[accumulators] combine/parallel_reduce
by Pavol Droba 18 Aug '08

18 Aug '08

Hi, I've just started to use the accumulators library. I must say that I like it a lot. However, I found one feature that I'm missing in the interface. In the time of multicore processors and Thread Building Blocks at hand, it would be nice to be able to use accumulators in parallel computations. To do so, one would need to combine partial computations. In other words, we need accumulator_set::combine(). This would combine the partial computation state from another accumulator_set. This operation would enable the accumulators to be used with parallel_reduce. I'm not expert in statistical computations, but as far as I can see, this should be doable quite easily. Best Regards, Pavol.

3 4

[doc] General Boost documentation suggestion
by Edward Diener 18 Aug '08

18 Aug '08

This is an impassioned plea for all library developers writing documentation about classes and/or functions ( including class templates and function templates ). Please, please put somewhere in the low-level description/explanation of that class and function both the full namespace it is in and the header file which must be included. Numerous times, using the functionality of an otherwise wonderful Boost library, I have had to hunt through the rest of that library's documentation to find the full namespace and header file which must be included in order to correctly use a particular function or class. This is irritatingly time consuming and can be remedied in all cases by the suggestion above. Thank you !

3 3

[shared_ptr][exception] Support for disabled RTTI
by Daniel James 18 Aug '08

18 Aug '08

Using boost with RTTI disabled was recently discussed on the user list, and I had a quick look into it. It seems that shared_ptr added support for the BOOST_NO_TYPEID macro in 1.35: http://svn.boost.org/trac/boost/ticket/1108 But because it now depends on the new exception library, which requires RTTI, it no longer works. Would it be possible to support the macro in Boost.Exception? Daniel

5 8

[shifted_ptr] STL support: 99%
by Phil Bouchard 18 Aug '08

18 Aug '08

Ok, this is awesome. Last week I made changes in the Sandbox I had to revert and rework all over... Now the changes I made in both the pointer and the STL containers are clearly to ones I want to stick with. This brings up interesting concepts at the same time, such as: what should be the right parameter of allocator::deallocate() ? We can't use a raw pointer over there. We can see the non-official patch inside the bits folder and shifted_allocator.hpp which I think solves the problem correctly. Furthermore allocator::allocate() I beleive shouldn't return yet a smart pointer because it creates unnecessary temporaries which can be costly, depending on the smart pointer used. So the typedefs inside shifted_allocator are the way I think they should be understood by the containers... Thanks, -Phil

4 15

"SuperC"
by Phil Bouchard 18 Aug '08

18 Aug '08

Here is a discussion I started with Gordon 2 weeks ago and I wanted to share globally because of its interesting features which aren't related to smart pointers: "I think a huge container inside an application will always suffer from imperfections and this could be a decent alternative to the problem. A map mixed with a list, a vector mixed with a set or all four together offers an infinite set of properties. Let's put it this way. All new "unordered" and multiset containers could easily be implemented as: 1) superc1st<double, list, vector> s1; 2) superc2nd<string, double, map, vector> s2; 3) superc2nd<string, double, map, map> s3; Where (explicit specializations for sake of example and please disregard missing "typename"s): 1) template <> class superc1st<double, list, vector> : public _list<0, void, double>, _vector<1, void, double> {...}; Here are examples of its usage: s1.push_back(5.7); s1[0] = 5.8; 2) template <> class superc2nd<string, double, map, vector> : public _map<0, string, double>::base, _vector<1, string, double>::base {...}; This one can be accessed as such: s2["Height"] = 6.3; // <-- O(log n) s2[10] = 5.9; // <-- O(1) 3) template <> class superc2nd<string, double, map, map> : public _map<0, string, double>::base, _map<1, string, double>::base {...}; To access 3) we could add indexed types we can cast the container to:s3.get<0>()["Age"] = 31; The underscored containers will be defined as: template <int I, typename T, typename U> struct _map : std::map<T, U> { typedef std::map<T, U> base; base & get<I>() { return * this; } // explicit function spec. won't work here (should be Ith type pack cast) }; And: template <int I, typename T, typename U> struct _vector : std::vector<U> { typedef std::vector<U> base; ... }; ... I think this is very easy to implement, cleaner and much more flexible (can use vectors and no container can be forgotten). My brain kernel example already needs something similar extensively..." Thanks, -Phil

1 0

[1.36.0: Graph] unused variable warning in topological_sort.hpp
by Christoph Duelli 18 Aug '08

18 Aug '08

in boost/graph/topological_sort.hpp, line 40 is an unused variable (u): template <typename Edge, typename Graph> void back_edge(const Edge& u, Graph&) { throw not_a_dag(); } Would be great if that could be fixed for the next release. Keep up the great job! Best regards Christoph

1 0

[1.36.0: Serialization] unused variable warning in shared_ptr.hpp
by Christoph Duelli 18 Aug '08

18 Aug '08

in boost/serialization/shared_ptr.hpp, line 133: in the case of NOT "#ifdef BOOST_SERIALIZATION_SHARED_PTR_132_HPP" the variable file_version is not used. Could be fixed by replacing else #endif by else #else (void)file_version; #endif or something similar. Would be great if that could be fixed for the next release. Keep up the great job! Best regards Christoph

1 0

Roland Puntaier ist außer Haus.
by Roland Puntaier 18 Aug '08

18 Aug '08

Ich werde ab 18.08.2008 nicht im Büro sein. Ich kehre zurück am 30.08.2008.

1 0

[asio]: extending asio
by Andreas Pokorny 17 Aug '08

17 Aug '08

Hello, I would like to add more asynchronous event sources to asio, like: - input events for mouse, keyboard and joystick .. - window exposure, move, resize events in some generic form, - generic "quit" events - file alteration With directFB/X11/Unix/Linux most of that can be done directly through select or epoll. But since reading the message and parsing events is mostly done by a third party library, I would only need the reactor part for these. Is this possible with asio? According to msdn it seems to be possible to create so called event objects for direct input devices. I am no win32 expert so I do not know if one can combine that with completion ports? Regards Andreas Pokorny

7 16

[swap] Renaming boost_swap_impl::swap_impl and/or its namespace?
by Niels Dekker - mail address until 2008-12-31 16 Aug '08

16 Aug '08

The boost::swap utility forwards its task to a helper function, ::boost_swap_impl::swap_impl. I /think/ that this top-level namespace, "boost_swap_impl", is there only "for historical reasons", because it was part of an ADL barrier. This ADL barrier is now replaced by a superior technique to avoid ambiguity, giving boost::swap an extra template argument as suggested by Steven Watanabe: // From http://svn.boost.org/svn/boost/trunk/boost/utility/swap.hpp namespace boost { template<class T1, class T2> void swap(T1& left, T2& right) { ::boost_swap_impl::swap_impl(left, right); } } So now I think it's preferable to remove the top-level namespace, "boost_swap_impl", and move the helper function into the boost namespace. For instance within a new nested namespace, boost::swap_impl_detail. Right? The name "boost::swap_impl_detail" should indicate to the user that she should not call swap_impl directly, because it's only an "implementation detail" of boost::swap. Or would it be preferable to have the swap_impl function "officially" accessible to the end user? If so, we might move swap_impl to the boost namespace, and rename it to something more "user friendly". (I would like to have it named, e.g., "boost::swap_using_adl".) I can think of two reasons why end-users might want to call swap_impl directly, instead of calling boost::swap: It /might/ in some cases, on /some/ platforms, perform /slightly/ better than boost::swap, because it would skip one function call. And secondly, swap_impl allows the user to specify the type of both function arguments by one single template argument. While the current boost::swap utility no longer does. For example: class animal_base_class {}; class cat_class : public animal_base_class {}; class dog_class : public animal_base_class {}; void swap(animal_base_class &, animal_base_class &) {} int main() { cat_class cat; dog_class dog; std::swap<animal_base_class>(cat, dog); // Okay. boost_swap_impl:: swap_impl<animal_base_class>(cat, dog); // Better: using ADL. boost::swap<animal_base_class>(cat, dog); // Compile error! } Of course we could also just keep the swap_impl function as an unsupported "implementation detail" for a while, until a user might want to use it... What do you think? -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center

4 13

Boost 1.36.0 release notice
by Beman Dawes 15 Aug '08

15 Aug '08

Boost 1.36.0 has been released and is available from SourceForge. See http://sourceforge.net/projects/boost/ This release include four new libraries: * Accumulators: Framework for incremental calculation, and collection of statistical accumulators, from Eric Niebler. * Exception: A library for transporting of arbitrary data in exception objects, and transporting of exceptions between threads, from Emil Dotchevski. * Units: Zero-overhead dimensional analysis and unit/quantity manipulation and conversion, from Matthias Schabel and Steven Watanabe * Unordered: Unordered associative containers, from Daniel James. Updated libraries include Asio, Assign, Function, Hash, Interprocess, Intrusive, Math, MPI, Multi-index Containers, PtrContainer, Spirit, Thread, Wave, and Xpressive. The release managers were Beman Dawes, Rene Rivera, and Daniel James. One note of caution: the initial SourceForge release files were missing some of the documentation. If you downloaded before 16:00 UTC, August 14th, please download again to be sure to get the full distribution. Sorry for the inconvenience! --Beman Dawes PS: The 1.36.0 version of the web site should be up within a few hours. If you can't wait, see http://beta.boost.org now!

4 5

AIX xlC error on static_move_ptr.hpp
by Gary Fu 15 Aug '08

15 Aug '08

Hi, Could anyone help why the AIX (5.3) xlC complains on the include file 'static_move_ptr.hpp' and how to solve the problem if possible ? I tried on Linux g++ without problem. Thanks, Gary 8:52pm > xlC -I $HOME/BOOST/boost_1_36_0 example.cpp -o example "/home_dir/Ggfu/BOOST/boost_1_36_0/boost/ptr_container/detail/static_move_ptr.hpp", line 182.22: 1540-2611 (S) The name "typename move_ptrs::enable_if_convertible<TT,T,boost::ptr_container_detail::static_move_ptr &>::type::type" can only be used to declare a constructor. #include <boost/ptr_container/detail/static_move_ptr.hpp> #include <iostream> #include <string> using namespace std; int main() { //print out the text string, "Hello, World!" cout << "Hello, World!" << endl; return 0; }

1 0

Issue building boost libs 1_35_0 on sparcv8 arch. with gcc 4.0.2
by Bhat, Aniket 15 Aug '08

15 Aug '08

FYI, I ran across a problem with the boost inline assembly code in boost_1_35_0/boost/detail/sp_counted_base_gcc_sparc.hpp. This file has inline assembly which uses the "cas" instruction. __asm__ __volatile__( "cas %0, %2, %1" : "+m" (*dest_), "+r" (swap_) : "r" (compare_) : "memory" ); Sparcv8 and pre-v8 architectures seem to be using the "swap" instruction instead. The native sparcv8 assembler therefore complains on trying to parse this: gcc.compile.c++ /home/cmchan/boost_libs/boost/bin.v2/libs/date_time/build/gcc-4.0.2/debu g/threading-multi/greg_month.o /var/tmp//ccMoGlpR.s: Assembler messages: /var/tmp//ccMoGlpR.s:1936: Error: Architecture mismatch on "cas". /var/tmp//ccMoGlpR.s:1936: (Requires v9|v9a|v9b; requested architecture is v8.) The file mentioned above is new in boost_1_35_0 and is included from boost_1_35_0/boost/detail/sp_counted_base.hpp: #elif defined(__GNUC__) && ( defined( __sparcv8 ) || defined( __sparcv9 ) ) Simply removing the pre-processing for __sparcv8 fixes the issue. I am not sure if this is really a tool-chain issue or the problem with the header boost_1_35_0/boost/detail/sp_counted_base.hpp Thanks, Aniket. <DIV><FONT size="1"> E-mail confidentiality. -------------------------------- This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. If you require assistance, please contact our IT department at helpdesk(a)spirent.com. Spirent Communications plc Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Tel No. +44 (0) 1293 767676 Fax No. +44 (0) 1293 767677 Registered in England Number 470893 Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Or if within the US, Spirent Communications, 26750 Agoura Road, Calabasas, CA, 91302, USA. Tel No. 1-818-676- 2300 </FONT></DIV>

1 0

Documentation skinning
by Emil Dotchevski 15 Aug '08

15 Aug '08

Perhaps I did something wrong, or failed to follow documentation rules, but the fact that the HTML files that I generated for Boost Exception were processed and wrapped in additional HTML caught me by surprise. Obviously I'm not against using uniform skin throughout Boost, but in general we can't just get HTML+CSS and wrap it with more HTML+CSS, there might be class name collisions, and whatnot. Besides the fact that now the Boost Exception documentation doesn't validate as XHTML 1.0, another problem is that some headings are simply function and class names, which the Boost CSS converts to allcaps, making them look like macros. It seems like other libraries have similar problems, I saw an instance of library documentation having its own tags indicating that it's HTML compliant, to which Boost is adding an additional XHTML 1.0 compliance tag, the end result being that the file is neither HTML or XHTML compliant. This is unfortunate and unprofessional. Is there a standardized XML format that can be used as documentation source? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

2 1

Compiling program_options v1.35 on msvc9.0 fix
by evert.vandewaal＠imtech.nl 15 Aug '08

15 Aug '08

Hi All, I have had some problems compiling program_options v1.35 on visual C++ 9.0 (2008) Express. It seems that this compiler does not correctly export some global variables when compiling to DLL, leading to unresolved dependencies. I have had to make a few changes: In file options_description.hpp, line 158: Replaced static const unsigned m_default_line_length; with BOOST_STATIC_CONSTANT (unsigned, m_default_line_length = 80); This is an old fix that I found in the mail archives (2005), seems to have been erroneously dropped from the base-line. In file options_description.cpp: removed the declaration of m_default_line_length. In file value_semantic.cpp: a singleton variable was defined but not properly linked by vc9.0. I changed the implementation to (line 17) BOOST_PROGRAM_OPTIONS_DECL string& arg() { static string* str=0; if (!str) { str = new string; *str = "arg"; } return *str; } At line 79 (after making the change above), I changed the only use of arg to: std::string untyped_value::name() const { return arg(); } In file details/value_semantic.hpp: I changed the declaration of the variable arg to (line 13): BOOST_PROGRAM_OPTIONS_DECL std::string& arg(); After these changes, program_options links properly, and I was able to run the demo code. Please note that also the pre-compiled version of boost 1.35 for the vc9.0 compiler from http://www.boost-consulting.com/download/windows suffers from these problems: the program_options DLL is unlinkable due to unresolved references to m_default_line_length and arg. Cheerio, Evert van de Waal

1 0

Re: [boost] Can multi-index do this?
by Gevorg Voskanyan 15 Aug '08

15 Aug '08

Daryle Walker wrote: [snip] > [1] Why isn't adaptor pushing done with "c.insert(c.end(), t)" > instead of "c.push_back(t)"? The "insert" method will work with > associative containers too. I guess because pop() can't be implemented reasonably with associative containers anyway. E.g. for stack pop() must know where the last pushed element got inserted up. That is straightforward with sequences but impossible (without some sort of extra bookkeeping) with associative containers. Best Regards, Gevorg

1 0