- Boost - lists.boost.org

[mpl] bug: has_xxx, default bool parameter
by Daniel Wallin 03 Sep '04

03 Sep '04

The traits generated with BOOST_MPL_HAS_XXX_TRAIT_DEF() doesn't work with lambda on VC7.1+. I think the problem is the default bool parameter: template< typename T, bool fallback_ = default_ > struct trait \ ^^^^^^^^^^^^^^^^^^^^^^^^^ This template will never match: template<template<typename ..> class F, class U1 .. UN> struct lambda<F<U1 .. UN> >; So lambda breaks. I guess the solution is to stop using a default bool parameter and use a class type instead. -- Daniel Wallin

2 1

[mpl] patch for config/has_xxx.hpp
by Jonathan Turkanis 03 Sep '04

03 Sep '04

Hi Aleksey, It looks like boost/mpl/aux_/config/has_xxx.hpp has an unnecesary include directive for boost/mpl/aux_/config/gcc.hpp. Jonathan begin 666 has_xxx.patch M26YD97@Z(&AA<U]X>'@N:'!P#0H]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T] M/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]#0I2 M0U,@9FEL93H@+V-V<W)O;W0O8F]O<W0O8F]O<W0O8F]O<W0O;7!L+V%U>%\O M8V]N9FEG+VAA<U]X>'@N:'!P+'8-"G)E=')I979I;F<@<F5V:7-I;VX@,2XR M#0ID:69F("UU("UR,2XR(&AA<U]X>'@N:'!P#0HM+2T@:&%S7WAX>"YH<' ) M,B!397 @,C P-" Q-3HT,#HT-2 M,# P, DQ+C(-"BLK*R!H87-?>'AX+FAP M< DR(%-E<" R,# T(#$X.C$P.C$X("TP,# P#0I 0" M,38L-R K,38L-B! M0 T*("\O("12979I<VEO;CH@,2XR("0-"B -"B C:6YC;'5D92 \8F]O<W0O M;7!L+V%U>%\O8V]N9FEG+V]V97)L;V%D7W)E<V]L=71I;VXN:'!P/@T*+2-I M;F-L=61E(#QB;V]S="]M<&PO875X7R]C;VYF:6<O9V-C+FAP<#X-"B C:6YC M;'5D92 \8F]O<W0O;7!L+V%U>%\O8V]N9FEG+W=O<FMA<F]U;F0N:'!P/@T* M( T*("\O(&%G=7)T+" Q,2]J86XO,#,Z('-I9VYA;',@82!S='5B+6]N;'D@ :)VAA<U]X>'@G(&EM<&QE;65N=&%T:6]N#0H` ` end

2 1

[BGL] Compilation failure of adjanceny_list on IBM
by Matthias Troyer 03 Sep '04

03 Sep '04

Since a recent CVS update the assignment operator of an adcacency_list graph fails to compile under the IBM vacpp compiler (xlC). The simplest test case is: #include <boost/graph/adjacency_list.hpp> int main() { typedef boost::adjacency_list<boost::vecS,boost::vecS,boost::directedS> G; G g; g = G(); } which fails as follows: "/users/matroyer/boost/boost/optional/optional.hpp", line 353.66: 1540-0210 (S) "T" is not a base class of "pair<boost::detail::out_edge_iter<std::_Ptrit<boost::detail:: sep_<unsigned long,boost::no_property>,long,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &>,unsigned long,boost::detail::edge_desc_impl<boost::directed_tag,unsigned long>,long>,boost::detail::out_edge_iter<std::_Ptrit<boo...". "/users/matroyer/boost/boost/optional/optional.hpp", line 353.10: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::pair<boost::detail:: out_edge_iter<std::_Ptrit<boost::detail::sep_<unsigned long,boost::no_property>,long,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &>,unsigned long,boost::detail::edge_desc_impl<boost::directed_tag,un...". "/users/matroyer/boost/boost/optional/optional.hpp", line 212.10: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::pair<boost::detail:: out_edge_iter<std::_Ptrit<boost::detail::sep_<unsigned long,boost::no_property>,long,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &>,unsigned long,boost::detail::edge_desc_impl<boost::directed_tag,un...". "/users/matroyer/boost/boost/graph/detail/adj_list_edge_iterator.hpp", line 38.11: 1540-0719 (I) The previous message was produced while processing the implicit member function "boost::detail::adj_list_edge_iterator<boost:: counting_iterator<unsigned long,boost::use_default,boost::use_default>,boost::detail:: out_edge_iter<std::_Ptrit<boost::detail::sep_<unsigned long,boost::no_property>,long,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsign...". "/users/matroyer/boost/boost/tuple/detail/tuple_basic.hpp", line 578.10: 1540-0700 (I) The previous message was produced while processing "boost::tuples::tuple<boost::detail::adj_list_edge_iterator<boost:: counting_iterator<unsigned long,boost::use_default,boost::use_default>,boost::detail:: out_edge_iter<std::_Ptrit<boost::detail::sep_<unsigned long,boost::no_property>,long,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,boost::no_property> &,boost::detail::sep_<unsigned long,boost::no_property> *,boost::detail::sep_<unsigned long,...". "/users/matroyer/boost/boost/graph/detail/adjacency_list.hpp", line 1943.19: 1540-0700 (I) The previous message was produced while processing "boost::vec_adj_list_impl<boost::adjacency_list<boost::vecS,boost:: vecS,boost::directedS,boost::no_property,boost::no_property,boost:: no_property,boost::listS>,struct boost::detail::adj_list_gen<class boost::adjacency_list<boost::vecS,boost::vecS,boost::directedS,boost:: no_property,boost::no_property,boost::no_property,boost::listS>,boost:: vecS,boost::vecS,boost::directedS,boost::no_property,boost:: no_property,boost::no_property,boost::...". "../../src/alps/lattice/unitcell.C", line 3.5: 1540-0700 (I) The previous message was produced while processing "main()" Can any of the BGL experts help? Matthias

1 0

RE: [boost] Java style GUI in C++
by Hurd, Matthew 03 Sep '04

03 Sep '04

> Behalf Of David Turner > Sent: Friday, 20 August 2004 3:32 AM > To: boost(a)lists.boost.org > Subject: RE: [boost] Java style GUI in C++ > > > I am currently designing a GUI framework in C++ (initially > > targeting the > > Windows platform) that uses a model similar to that which > > Java uses in it's > > AWT and Swing libraries. Specifically: > > [snip] > > > I would appreciate comments and ideas as to what people would > > like out of a > > GUI framework, especially one that will be multi-platform. > > > > Boost-style C++ GUI library utilizing boost::signals and with a nice way > of handling message loops: > > http://cxxgui.sf.net/ Looks like a very nice conservative approach. I think you're wise to keep it simple and take a conservative c++ approach. Only trouble is it still feels like a lot of other things just shines a bit brighter and has cleaner lines. However I must say I've never seen a UI lib I've been happy with. Nor have I written one, or infrastructure that uses one, that I've been fond of. I find even 200 lines of code (not cxxgui) for a simple split windows file explorer-like interface scary, but the sad thing is that it is a great improvement over the norm. Some rambling thoughts on things I'd like to see are: 1. run-time and compile-time configurability, especially with some like compile time specification language like layout capability. There was some talk about this and some suggestions previously on this list. Marrying this to run-time would be interesting. Perhaps at compile time you can decide if there is an explicit handling method and if not call something with your source and event type that will dispatch. However this would lock you in at run-time if did this as a compile time metaprogramming thing that ending up optimizing to a function call equivalent but perhaps both options are appropriate... 2. reverse structural inheritance of events handler equivalents. Widgets are composed of other widgets. A window may handle the click, or prevent it, for a child. You can attach a handler for a named event at any point in the composition / structural hierarchy, it doesn't have to be the source, but is aware of it. Handling goes down the hierarchy to source. 3. get rid of the distinction between properties, events and methods. Consider a widget a functor with visual side affects. Consider it like a dataflow where properties being set, events and method calls are just messages coming into this node. Allows you to interpose handlers, recorders, do nice testing and all sorts. Draw backs are interoperability with initialization requirements of widgets. That is, some things are set at widget create time. But this might handled by avoiding by not changing such parameters and thus not needing to change, but if initialization only parameters of legacy components change, then destroy and recreate the component. 4. Structural context sensitivity, 4a inherit properties from your run-time structural parents, fonts, colours, whatever, perhaps from theme packages that are higher in the tree. The structural tree is used to find the appropriate handler for properties, events and methods (all one in the same) 4b Context sensitive addressing and sources. Just like event handling, property setting and method calls are sinks that are handled with structural sensitivity, sources, such as changing properties, data propagation flow out and can be addressed in a context sensitive manner. E.g. if you have a widget that is expecting an source for stock code, it should look up the structural hierarchy to find it, unless it is provided with an explicit mapping to a different source. Allow non UI components that can act as holders for properties (like a root blackboarding thingo (technical term) ) so that components can reflect context of non-parental nodes. 4c Context sensitive addressing. Want to be able to get the properties / sources of siblings, i.e. children of parents of yours. "Instrument" -> "maturity". You find the parent and then lock into its context for a piece of detail. 5. must be multiplatform, leveraging off something like wxwidgets like notus does for its implementation layer would probably be a good idea. 6. must have a wysiwyg designer (though I could live without it) (self hosting would be a neat goal) - integrating the compiler into this and being an ide would be nice - perhaps something like eclipse could help 6a Because of the run configurability of everything there is nothing to stop external descriptions of components, including the mapping of sources to sinks to capture most of the requirements. Obviously where code is needed you need code and an xml resource description will not help. 7. Should support run time type conversions to allow easy hooking up of stuff. Not sure how explicit or implicit this should be. A while ago I did something like this that also supported the dimensionality of the data so you could cut, slice and aggregate stuff easily between widgets. E.g. use the entire list, the selected items, etc... would take some kind of multidimensional iterator thing I guess. Allows some sophisticated run-time modelling capabilities. See the data in a grid, or a list control, a combo, .... With this kind of structure you should be able to compose widgets hierarchies that have awareness of the others around them and will have reasonable normal functionality without too much coding at all. Supporting this at run time as well allows you to have some nice drag / drop or otherwise dynamic configurability. Have some that get a list of strings, displays it in a list. Click on a list item and a chart and grid automatically updates. A detailed pane of items relevant to the first click docked at the side updates. The exit item in the menu does the default behaviour of shutting down the application. My goal is that this should be possible with out an enormous number of lines of code. Structurally specify it. Use context sensitivity, standardish workflows and data set handling / iterator capabilities to avoid code. Thwack custom events in where needed. Been thinking about this for years and have implemented various systems that do bits of this approach. Enough to know it works pretty well. It has always been too much work to chew on as a generic solution though... $0.005, Matt. Side issue: resizing / device independence. Problem with swing / wxwidget sizers and the like is that you can end up with some ugly looking screens with lots of space, things that are too small on screen sizes that are inappropriate. A lot of the time it doesn't matter too much, but often enough to irk me the screens just don't look "sharp" enough compared to an explicitly designed screen. This is often the issue with smaller screen sizes like portable devices. Something I've done in the past is to give components fractions of resizing for top, left, height and width which allows a tight design, to the pixel ( I really like the compile time unit dimensioning of the co-ords by the way, positioning by mm dimensions is great) with easier control on how the thing will resize. Also for device independence you might be able to target a different device by using a capability set where controls map to other controls for that device, they just have to handle the same sources and sinks for their node, i.e. have the same conceptual support. Perhaps that be a nice level of indirection to solve problems. Use a tree control, grid or list or whatever, just don't specific which. The platform configuration maps in the explicit control. Is you use a more refined control that is not available on that specific platform, you can substitute a generic one based on a substitutability principle (like Liskov SP), or perhaps it is an error (perhaps the design can specific the functionality that must exist for the there to be no error). A thin client approach to this would be even nicer, separate the visual aspects from the data it refers to by protocol and/or method call so that interesting thin / thick / adaptive clients can be built. IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

6 17

Boost::Python iterators are off by 1?
by Dan Eloff 03 Sep '04

03 Sep '04

If this is my fault the docs need to be more explanatory, but here's the problem: for the sequence (0, 1, 2), the Boost::Python iterator starts at 1 and ends 1 past 2 ( where 3 might be ). It does this because it calls the C++ iterators functions in this order: operator == post-increment dereference It should imho call them like (which would correct the issue) operator == dereference post-increment Like a normal for loop would execute: condition, code, action. The code to reproduce this is: #include <iterator> #include <boost/python.hpp> namespace py = boost::python; struct ctn { struct iterator: public std::iterator< std::input_iterator_tag, py::str > { int mNum; iterator( int num = 0 ): mNum( num ) {} py::str operator *() const { char temp[20]; const char * str = itoa( mNum, temp, 10 ); return py::str( str, strlen( str ) ); } iterator& operator ++(int) { mNum++; return *this; } friend bool operator ==( iterator lhs, iterator rhs ) { return ( lhs.mNum == rhs.mNum ); } }; iterator begin() { return iterator( 0 ); } iterator end() { return iterator( 3 ); // the range (0, 1, 2) three items } }; BOOST_PYTHON_MODULE(iter_bug) { py::class_< ctn >( "ctn" ) .def( "__iter__", py::iterator< ctn >() ) ; } >>> from iter_bug import * >>> c = ctn() >>> for i in c: ... print i ... 1 2 3 >>> Notice how it's off by one because of the very strange order of doing things. Please help! -Dan

2 8

[test][vacpp] problem with Boost.Test under IBM VisualAge C++ V6.0 for AIX
by JOAQUIN LOPEZ MU?Z 03 Sep '04

03 Sep '04

Many tests are failing with the following "/home/tk/boost_regression/boost/libs/test/src/unit_test_result.cpp", line 147.61: 1540-0130 (S) "std::__log10" is not declared. I've taken a look at the offending file and seems nothing has changed in the past months with respect to the usage of std::log10, so I guess this will have to do with some problem or misconfiguration in vacpp std lib. Any idea? Thank you Joaquín M López Muñoz Telfónica, Investigación y Desarrollo

3 3

[Boost-bugs] [ boost-Bugs-1021799 ] struct pointer_iterator_traits<T*> fails on VC7.1
by SourceForge.net 03 Sep '04

03 Sep '04

Bugs item #1021799, was opened at 2004-09-03 14:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1021799&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marvin H. Sielenkemper (sielenk) Assigned to: Nobody/Anonymous (nobody) Summary: struct pointer_iterator_traits<T*> fails on VC7.1 Initial Comment: We are using boost::iterator_facade in our project. During compilation we got an error: c:\Boost\include\boost-1_31\boost\detail\iterator.hpp (270) : warning C4346: 'boost::remove_const<T>::type' : dependent name is not a type The error was caused by class k_EntryIterator : public boost::iterator_facade<k_EntryIterator, r_DirectoryEntry, boost::single_pass_traversal_tag> { public: k_EntryIterator(k_DirectoryInfo& ak_Owner); ~k_EntryIterator(); private: friend class boost::iterator_core_access; k_DirectoryInfo& mk_Owner; void increment(); bool equal(k_EntryIterator const& other) const; r_DirectoryEntry& dereference() const; }; and was easily fixed by adding a 'typename' in line 270 of iterator.hpp: old: typedef remove_const<T>::type value_type; new: typedef typename remove_const<T>::type value_type; MfG, Marvin H. Sielenkemper ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1021799&group_… ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

compile-time variables
by Goran Mitrovic 03 Sep '04

03 Sep '04

I've got a question. Is a compile-time variables concept known? It would be a set of macros that would allow assigning and changing a number assigned to a variable's name. Such variable would be considered as a constant from template argument's perspective, for example. One of the usage for such classes I have in mind would be the painless type registration of typeof macro, for example...

6 8

An alternative typeof macro
by Daniel James 03 Sep '04

03 Sep '04

I've come up with an alternative way to invoke the typeof emulations that have been posted. It basically works by defining an iterator over the encoded type. Unfortunately, it can't be used inside a function, and is awkward to use in general, but has the advantage is that it only has to define the call to foo once, which might result in faster compile times. It could possibly also remove the limit on the complexity of the type. Arkadiy's version would require a some changes to do this, but I think Peder's could quite easily. Although I'm not sure as I've only had a brief look at his version. I've implemented it as a sort of typedef, which seems like the easiest way to use it. It's probably easier to understand the code than my explanation, so here it is. It's based on Arkadiy's version in the yahoo groups file section. #define BOOST_TYPEOF_TYPEDEF_ITERATOR_NAME(Name) \ BOOST_PP_CAT(BOOST_TYPEOF_TYPEDEF_ITERATOR_##Name##_, __LINE__) #define BOOST_TYPEOF_TYPEDEF_ITERATOR(Expr, Name) \ struct BOOST_TYPEOF_TYPEDEF_ITERATOR_NAME(Name) { \ template <int pos> \ struct iterator { \ typedef boost::mpl::int_< \ sizeof(boost::type_of::foo<pos>(Expr))> type; \ typedef iterator<pos+1> next; \ }; \ }; #define BOOST_TYPEOF_TYPEDEF(Expr, Name) \ BOOST_TYPEOF_TYPEDEF_ITERATOR(Expr, Name) \ typedef boost::type_of::decode_type< \ BOOST_TYPEOF_TYPEDEF_ITERATOR_NAME(Name)::iterator<0> \ >::type Name; #define BOOST_TYPEOF_TPL_TYPEDEF(Expr, Name) \ BOOST_TYPEOF_TYPEDEF_ITERATOR(Expr, Name) \ typedef typename boost::type_of::decode_type< \ BOOST_TYPEOF_TYPEDEF_ITERATOR_NAME(Name)::iterator<0> \ >::type Name; Here is an example of it's use: template <class Op> struct result_of_nullary_functor { static Op op; BOOST_TYPEOF_TPL_TYPEDEF(op(), type); }; struct g { int operator()(); }; BOOST_MPL_ASSERT_IS_SAME(result_of_nullary_functor<g>::type, int); I've only tested on the intel linux compiler. Daniel

5 38

RE: [boost] Porting to SCO Unix
by Ben Hutchings 03 Sep '04

03 Sep '04

John Maddock <john(a)johnmaddock.co.uk> wrote: > > The following tests in libs/config/configure produce incorrect > > results: > > > > ** checking for pthread_exit in -lpthread... no > > This test tries to compile a C source file that prototypes > > "pthread_exit" as "char pthread_exit();". But my compiler driver > > always adds "-include <...>/pthread.h" to the command line, which > > includes a different, conflicting prototype for this function. I > > think the test ought to include <pthread.h> instead. > > Grrrrr, I used the standard autoconf macros for checking this, if I > get the time I'll try and write my own version that does what you > suggest. > > > ** checking pthread_yield... no > > This is correct, but I do have a pthread_yield_np() function, > > maybe we should look for it, too. > > It's up to the thread lib guys to use it (or not), maybe you could > hassle the authors of the thread lib you are using to provide a > standard function signature? pthread_yield is non-standard; you should use sched_yield instead (if at all). See <http://groups.google.com/groups?selm=3ecbb70c%40usenet01.boi.hp.com>

2 1