August 2004 - Boost - lists.boost.org

[signals] trackable object limitations
by Jeff Flinn 19 Aug '04

19 Aug '04

Any changes in 1.32 pertaining to: Warning: User-defined function objects and function objects from other libraries (e.g., Boost.Function or Boost.Lambda) do not implement the required interfaces for trackable object detection, and will silently ignore any bound trackable objects. Future versions of the Boost libraries will address this limitation. Thanks, Jeff

2 1

typeof and ODR
by Arkadiy Vertleyb 19 Aug '04

19 Aug '04

David Abrahams wrote: >We should try this stuff [typeof] out with EDG-based compilers in their >"template repository" link-time-instantiation mode. Also I think >Metrowerks now supports the same thing. These are the most likely >configurations to report problems from ODR violations. Can anybody help me with this? (I do realize that it's not a good timing now, but I just want to see if I can count on it once things get quieter) Thanks in advance, Arkadiy

1 0

test_read_write_mutex trouble under Tru64 Unix
by Ralf W. Grosse-Kunstleve 19 Aug '04

19 Aug '04

Last night I started Aleksey's regression.py script under Tru64 Unix. It used to finish after 6 hours, but now the test_read_write_mutex process has consumed 16 CPU hours already without finishing. I am going to kill it. I hope the failure shows up at the meta-comm site. Let me know if more information is required. Ralf _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush

3 3

Re: [boost] Java style GUI in C++
by Reece Dunn 19 Aug '04

19 Aug '04

John Torjo wrote: >Hi Reece, > >Just a few thoughts: > >>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 > >Take a deep breath if you want to make it cross-platform ;) >I think that's Windows work x 10 or so. Maybe more ;) ... I was thinking about having a compatibility layer, e.g.: namespace windows { class window { public: inline handle_type create( const string_type title, ... ); inline void set_size( long, long ); // ... }; } namespace linux{ class window{ ... }; } Then engineer the library on top of that. This would simplify x-platform development... the problem is working out the right abstraction. >>it's AWT and Swing libraries. Specifically: >> >>[1] Being able to use constructors to create the windows/components. This >>means there is no need to explicitly call a Create method like in the MFC >>framework. > >win32gui does that ;) :) I am having a look at all the links to the various libraries, so it may take a while to process them all. (Thanks for everyone who compiled the links). >>[2] The use of layout managers. I like the various layout managers in Java >>and how easy it is to construct complex GUI interfaces. > >I like the idea of layout managers. Still, it seems (to me) in real-life >they kind of fail. You'll always want that special case where you need to >hide control X and show control Y, etc. So why not have that ability in the framework? That is the reason I posted this, to get ideas. It should not be that difficult to be able to change the layouts at run-time... once the layout managers have been written, that is. >So far, I've created splitters on dialogs at design time (still beta ;)). >If you use them correctly, you can specify a lot ot design time. Also, you >can easily hide/show the left/right panes. cool. >>[3] The support for events via "listeners". This will most likely be >>geared towards key/mouse events and "action" events (e.g. when the user >>presses on a button). > >I'm not a big fan of listeners. You need to do a lot of coding manually to >set them, etc. I've implemented them totally different - using event >handler classes. My idea was something along the lines of: class MouseEvent { public: static const int LeftButton = 0; static const int MiddleButton = 1; static const int RightButton = 2; private: int button; unsigned int vkeys; win::api::point pt; public: inline MouseEvent( int, WPARAM, LPARAM ); }; MouseEvent::MouseEvent( int btn, WPARAM wp, LPARAM lp ): button( btn ), vkey( wp ), pt( lp ) { } class MouseListener { public: virtual void mouseMove( const MouseEvent & ); virtual void mouseButtonDown( const MouseEvent & ); virtual void mouseButtonUp( const MouseEvent & ); virtual void mouseButtonDoubleClick( const MouseEvent & ); public: virtual ~MouseButtonListener(); }; With a common listener interface for GUI object actions, e.g. pressing a mouse button, selecting an item in a listbox, editing text, etc. >>At the moment, I have a basic working version that allows you to write the >>following: >> >>int PASCAL WinMain( HINSTANCE, HINSTANCE, LPSTR, int sw ) >>{ >> swing::JFrame frame( L"Swing JFrame!" ); >> frame.setPane( new swing::JPanel()); >> frame.setSize( 500, 500 ); >> frame.show( sw ); >> >> MessageLoop msg; >> return( msg.Execute()); >>} > >can you break the message loop? >That is, specify when a message loop should end (when a certain signal is >received). You can call ::PostQuitMessage( 0 ), but that is Windows specific. At the moment the message loop doesn't do anything fancy (accelerator/dialog box message processing), but it is on the list of things to work on. >>This creates two windows: the main frame and a panel that is a child of >>that frame. The JFrame is created in the constructor, but is not displayed >>until show is called. Likewise, the JPanel is created inside its >>constructor and the JFrame.setPane method makes that window a child of the >>frame. >> >>I would appreciate comments and ideas as to what people would like out of >>a GUI framework, especially one that will be multi-platform. > >I'm all for it, but again, I think it's so much work... But it will be fun! :D Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

4 4

[Boost-bugs] [ boost-Bugs-1012135 ] boost::filesystem is systematically broken
by SourceForge.net 19 Aug '04

19 Aug '04

Bugs item #1012135, was opened at 2004-08-19 14:01 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=1012135&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Carlo Wood (libcw) Assigned to: Nobody/Anonymous (nobody) Summary: boost::filesystem is systematically broken Initial Comment: As is currently discussed on the boost mailinglist, cygwin is supposed to support windows paths (at least, when compiled with BOOST_WINDOWS, which is currently the default). I understand that Beman, the author of boost::filesystem, wants it that way. However, boost::filesystem does not accept a path like "/usr" (fs::exists fails in that case), when compiled with BOOST_WINDOWS and it *also* doesn't accept windows paths, like "c:/cygwin/usr", "C:\cygwin\usr" or anything remotely 'windows' like, because it throws when you try to construct a fs::path with a colon in it! As a result, one can ONLY construct usable paths on cygwin in the very non-portable format "/cggdrive/c/cygwin/usr" which is neither POSIX (on linux the same path would be "/usr") nor native (the _users_ of the application will view this path as "C:\cygwin\usr"). It is 100% cygwin specific. OR one has to construct paths on cygwin using 'native' all the time (or no_check) as path checker, because even windows_name doesn't work :/ Consider the following code: #include <iostream> #include <boost/filesystem/path.hpp> #include <boost/filesystem/operations.hpp> int main() { try { boost::filesystem::path p("C:\cygwin\usr", &boost::filesystem::windows_name); } catch(std::exception const& error) { std::cerr << "Exception: " << error.what() << std::endl; } } With the following result: Exception: boost::filesystem::path: invalid name "C:\cygwin\usr" in path: "C:\cygwin\usr" Same thing with any other variation that starts with 'C:'. I believe that this is a structural failure of boost::filesystem, revealing a major error in the design. A re-design seems to be in order before it can be considered to be usable in multi-platform applications. The most important problem with the current design is that a single type (namely fs::path) is being used for effectively two different types: canonical paths and native paths. A new design should provide a new type, fs::native_path that cannot be mixed with the canonical path representation. This native_path should have builtin checks that are native and fs::path should only check for portability (and allow relaxation of that when lesser OS need to be supported). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1012135&group_… ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: Java style GUI in C++
by Johannes Brunen 19 Aug '04

19 Aug '04

Hi, Edward Diener wrote: > Why not use boost::signals for your event interface. It is much better than > hand-coded actions and listeners, since any type of function can handle an > event. The technology is already in Boost so why re-invent the wheel. I would like to emphazise this. I use the boost signal library for handling the tree view control and list view control events in an extension of the Zinc gui library. It works pretty well. Johannes

1 0

Re: Re: Java style GUI in C++
by Johannes Brunen 19 Aug '04

19 Aug '04

Hi, Pavel Vozenilek wrote: > To stop it: ultimate list of all (dozens) known GUI frameworks > is on http://www.free-soft.org/guitool/. I'm well aware of the link. But it is not up to date. For instance http://www.torjo.com/win32gui/ and http://notus.sourceforge.net/ aren't mentioned at all. http://gtkmm.sourceforge.net/ valuation is not correct with respect to the win32 platform. For some time I'm searching for the ultimate GUI framework. I didn't know of TnFox, Notus and Ultimate++. So I learned something from the contributions. Johannes

1 0

lightweight replacement for boost::function
by John Torjo 19 Aug '04

19 Aug '04

Dear boosters, Did a lightweight replacement for boost::function (compile-wise). Focus was on making it very fast to compile. Rationale: boost::function takes too long to compile. In a library I'm developing (win32gui), using boost::function would almost double the compilation time of some headers. This lightweight replacement takes virtually no extra compilation time. How I tested it: I took a project that took 1 minute to compile - added this to all of the headers, and it compiles in the same amount of time. #including <boost/function.hpp> almost doubled the time. Tested with vc71,gcc3.2. Feel free to use it any way you wish. Any feedback/suggestions deeply appreciated. Best, John -- John Torjo Freelancer -- john(a)torjo.com Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -- v1.3beta released - check out splitter/simple_viewer, a File Explorer/Viewer all in about 200 lines of code! Professional Logging Solution for FREE -- http://www.torjo.com/code/logging.zip (logging - C++) -- http://www.torjo.com/logview/ (viewing/filtering - Win32) -- http://www.torjo.com/logbreak/ (debugging - Win32) #ifndef JOHN_TORJO_WIN32GUI_function #define JOHN_TORJO_WIN32GUI_function #if defined(_MSC_VER) && (_MSC_VER >= 1020) # pragma once #endif // function.hpp // Win32 GUI Generics library // // Copyright (C) 2004 John Torjo (john(a)torjo.com) // // Permission to copy, use, sell and distribute this software is granted // provided this copyright notice appears in all copies. // Permission to modify the code and to distribute modified code is granted // provided this copyright notice appears in all copies, and a notice // that the code was modified is included with the copyright notice. // // This software is provided "as is" without express or implied warranty, // and with no claim as to its suitability for any purpose. // // To see the version you have now, read win32gui/version.txt // // You can find the latest version of this library at http://www.torjo.com/win32gui/ #include <assert.h> #include <stdexcept> // #include <win32gui/.hpp> namespace win32 { namespace gui { /* Note: removed dependency on boost, and anyway, boost::function does take a lot to compile */ // note: removed dependency on boost, that's why we need this namespace detail { struct no_param {}; template<class func, class base> struct func_exec : base { typedef typename base::result res; typedef typename base::arg1 arg1; typedef typename base::arg2 arg2; typedef typename base::arg3 arg3; typedef typename base::arg4 arg4; typedef typename base::arg5 arg5; func_exec(func f) : f(f) {} // note: one of these is defined virtual in class base res operator()() { return f(); } res operator()(const arg1 & a1) { return f(a1); } res operator()(const arg1 & a1, const arg2 & a2) { return f(a1,a2); } res operator()(const arg1 & a1, const arg2 & a2, const arg3 & a3) { return f(a1,a2,a3); } res operator()(const arg1 & a1, const arg2 & a2, const arg3 & a3, const arg4 & a4) { return f(a1,a2,a3,a4); } res operator()(const arg1 & a1, const arg2 & a2, const arg3 & a3, const arg4 & a4, const arg5 & a5) { return f(a1,a2,a3,a4,a5); } // overrides the base' class base * clone() const { return new func_exec<func,base>(*this); } private: func f; }; template<class res> struct func_keeper0 { typedef func_keeper0<res> self; typedef res result; typedef no_param arg1; typedef no_param arg2; typedef no_param arg3; typedef no_param arg4; typedef no_param arg5; virtual res operator()() = 0; virtual self * clone() const = 0; }; template<class res, class a1> struct func_keeper1 { typedef func_keeper1<res,a1> self; typedef res result; typedef a1 arg1; typedef no_param arg2; typedef no_param arg3; typedef no_param arg4; typedef no_param arg5; virtual res operator()(const arg1&) = 0; virtual self * clone() const = 0; }; template<class res, class a1, class a2> struct func_keeper2 { typedef func_keeper2<res,a1,a2> self; typedef res result; typedef a1 arg1; typedef a2 arg2; typedef no_param arg3; typedef no_param arg4; typedef no_param arg5; virtual res operator()(const arg1&,const arg2&) = 0; virtual self * clone() const = 0; }; template<class res, class a1, class a2, class a3> struct func_keeper3 { typedef func_keeper3<res,a1,a2,a3> self; typedef res result; typedef a1 arg1; typedef a2 arg2; typedef a3 arg3; typedef no_param arg4; typedef no_param arg5; virtual res operator()(const arg1&,const arg2&, const arg3&) = 0; virtual self * clone() const = 0; }; template<class res, class a1, class a2, class a3, class a4> struct func_keeper4 { typedef func_keeper4<res,a1,a2,a3,a4> self; typedef res result; typedef a1 arg1; typedef a2 arg2; typedef a3 arg3; typedef a4 arg4; typedef no_param arg5; virtual res operator()(const arg1&,const arg2&, const arg3&, const arg4&) = 0; virtual self * clone() const = 0; }; } template<class res> struct func_wrapper0 { typedef res result; typedef detail::no_param arg1; typedef detail::no_param arg2; typedef detail::no_param arg3; typedef detail::no_param arg4; typedef detail::no_param arg5; typedef detail::func_keeper0<res> func_keeper; typedef func_wrapper0<res> self_type; func_wrapper0() : m_f(0) {} template<class func> func_wrapper0(func f) : m_f(new detail::func_exec<func,func_keeper>(f)) {} typedef res (*raw_func)(); func_wrapper0(raw_func f) : m_f(new detail::func_exec<raw_func,func_keeper>(f)){} func_wrapper0(const self_type & other) : m_f(other.m_f ? other.m_f->clone() : 0) {} res operator()() { if ( m_f) return (*m_f)(); else WIN32GUI_THROW std::runtime_error("null function"); } self_type& operator=(const self_type & other) { func_keeper * old = m_f; m_f = other.m_f ? other.m_f->clone() : 0; delete old; return *this; } private: func_keeper * m_f; }; template<class res,class arg1_type> struct func_wrapper1 { typedef res result; typedef arg1_type arg1; typedef detail::no_param arg2; typedef detail::no_param arg3; typedef detail::no_param arg4; typedef detail::no_param arg5; typedef detail::func_keeper1<res,arg1> func_keeper; typedef func_wrapper1<res,arg1> self_type; typedef res (*raw_func)(const arg1&); func_wrapper1() : m_f(0) {} template<class func> func_wrapper1(func f) : m_f(new detail::func_exec<func,func_keeper>(f)) {} func_wrapper1(raw_func f) : m_f(new detail::func_exec<raw_func,func_keeper>(f)){} func_wrapper1(const self_type & other) : m_f(other.m_f ? other.m_f->clone() : 0) {} res operator()(const arg1 &a1) { if ( m_f) return (*m_f)(a1); else WIN32GUI_THROW std::runtime_error("null function"); } self_type& operator=(const self_type & other) { func_keeper * old = m_f; m_f = other.m_f ? other.m_f->clone() : 0; delete old; return *this; } private: func_keeper * m_f; }; template<class res,class arg1_type,class arg2_type> struct func_wrapper2 { typedef res result; typedef arg1_type arg1; typedef arg2_type arg2; typedef detail::no_param arg3; typedef detail::no_param arg4; typedef detail::no_param arg5; typedef detail::func_keeper2<res,arg1,arg2> func_keeper; typedef func_wrapper2<res,arg1,arg2> self_type; typedef res (*raw_func)(const arg1&,const arg2&); func_wrapper2() : m_f(0) {} template<class func> func_wrapper2(func f) : m_f(new detail::func_exec<func,func_keeper>(f)) {} func_wrapper2(raw_func f) : m_f(new detail::func_exec<raw_func,func_keeper>(f)){} func_wrapper2(const self_type & other) : m_f(other.m_f ? other.m_f->clone() : 0) {} res operator()(const arg1 &a1, const arg2 &a2) { if ( m_f) return (*m_f)(a1,a2); else WIN32GUI_THROW std::runtime_error("null function"); } self_type& operator=(const self_type & other) { func_keeper * old = m_f; m_f = other.m_f ? other.m_f->clone() : 0; delete old; return *this; } private: func_keeper * m_f; }; template<class res,class arg1_type,class arg2_type,class arg3_type> struct func_wrapper3 { typedef res result; typedef arg1_type arg1; typedef arg2_type arg2; typedef arg3_type arg3; typedef detail::no_param arg4; typedef detail::no_param arg5; typedef detail::func_keeper3<res,arg1,arg2,arg3> func_keeper; typedef func_wrapper3<res,arg1,arg2,arg3> self_type; typedef res (*raw_func)(const arg1&,const arg2&,const arg3&); func_wrapper3() : m_f(0) {} template<class func> func_wrapper3(func f) : m_f(new detail::func_exec<func,func_keeper>(f)) {} func_wrapper3(raw_func f) : m_f(new detail::func_exec<raw_func,func_keeper>(f)){} func_wrapper3(const self_type & other) : m_f(other.m_f ? other.m_f->clone() : 0) {} res operator()(const arg1 &a1, const arg2 &a2, const arg3 &a3) { if ( m_f) return (*m_f)(a1,a2,a3); else WIN32GUI_THROW std::runtime_error("null function"); } self_type& operator=(const self_type & other) { func_keeper * old = m_f; m_f = other.m_f ? other.m_f->clone() : 0; delete old; return *this; } private: func_keeper * m_f; }; template<class res,class arg1_type,class arg2_type,class arg3_type,class arg4_type> struct func_wrapper4 { typedef res result; typedef arg1_type arg1; typedef arg2_type arg2; typedef arg3_type arg3; typedef arg4_type arg4; typedef detail::no_param arg5; typedef detail::func_keeper4<res,arg1,arg2,arg3,arg4> func_keeper; typedef func_wrapper4<res,arg1,arg2,arg3,arg4> self_type; typedef res (*raw_func)(const arg1&,const arg2&,const arg3&,const arg4&); func_wrapper4() : m_f(0) {} template<class func> func_wrapper4(func f) : m_f(new detail::func_exec<func,func_keeper>(f)) {} func_wrapper4(raw_func f) : m_f(new detail::func_exec<raw_func,func_keeper>(f)){} func_wrapper4(const self_type & other) : m_f(other.m_f ? other.m_f->clone() : 0) {} res operator()(const arg1 &a1, const arg2 &a2, const arg3 &a3, const arg4 &a4) { if ( m_f) return (*m_f)(a1,a2,a3,a4); else WIN32GUI_THROW std::runtime_error("null function"); } self_type& operator=(const self_type & other) { func_keeper * old = m_f; m_f = other.m_f ? other.m_f->clone() : 0; delete old; return *this; } private: func_keeper * m_f; }; /* void f() { std::cout << "f" << std::endl; } void f1(int i) { std::cout << "f1(" << i << ")" << std::endl; } bool f2(int i, char c) { std::cout << "f2(" << i << "," << c << ")" << std::endl; return true; } int f3(int i, char c, char d) { std::cout << "f3(" << i << "," << c << d << ")" << std::endl; return 2; } int f4(int i, char c, char d, char e) { std::cout << "f4(" << i << "," << c << d << e << ")" << std::endl; return 3; } struct titi { titi() : idx(0) {} void operator()() { std::cout << "titi" << idx++ << std::endl; } int idx; }; int main() { func_wrapper0<void> test(&f); test(); titi t; func_wrapper0<void> test2( t ); test2(); func_wrapper0<void> test3( test2 ); test2(); test2(); test3(); func_wrapper0<void> test4; test4 = test3; test4(); test4 = test; test4(); func_wrapper1<void,long> func1(f1); func1(0); func1(2); func_wrapper2<int,long,int> func2(f2); int i = func2(10,97); assert(i == 1); func_wrapper3<int,long,int,char> func3(f3); i = func3(11,97,'b'); assert(i == 2); func_wrapper4<int,long,int,char,char> func4(f4); i = func4(12,97,'b','c'); assert(i == 3); std::cin.get(); return 0; } */ }} #endif // JOHN_TORJO_WIN32GUI_function

4 6

Java style GUI in C++
by Johannes Brunen 19 Aug '04

19 Aug '04

Hi Reece, did you know of the existence of the following list of C++ GUI frameworks? I think they are currently the most important ones. http://www.fltk.org/index.php http://www.fox-toolkit.org/ http://gtkmm.sourceforge.net/ http://inti.sourceforge.net/ http://www.trolltech.com/ http://vcf.sourceforge.net/ http://www.wxwindows.org/ http://www.torjo.com/win32gui/ All of them have some strength and some weaknesses. It may be worth to look at least at the gtkmm, vcf and the win32gui frameworks. Johannes

7 6

boost::noncopyable broken?
by Bronek Kozicki 19 Aug '04

19 Aug '04

Hello when testing some regression errors I updated my second local copy from anonymous CVS @ sf.net (first copy is always from meta-comm and is producing regression tests you can see on www.meta-comm.com) Then I started running some tests, and received many errors similar to following: (vc71) boost\noncopyable.hpp(32) : error C2371: 'boost::noncopyable' : redefinition; different basic types boost\utility_fwd.hpp(26) : see declaration of 'boost::noncopyable' boost\test\unit_test_log.hpp(138) : error C2504: 'boost::noncopyable' : base class undefined (como-win32-4.3.3-vc7.1) boost/noncopyable.hpp", line 32: error #256: invalid redeclaration of type name "boost::noncopyable" (declared at line 26 of "boost/utility_fwd.hpp") typedef noncopyable_::noncopyable noncopyable; ^ I then took archived boost.tar.bz2 from meta-comm (boost-04-08-18-1200) and found the same error in this archive. Fortunatelly I also have older copy of this archive (boost-04-08-18-0600) and this archive is currently used to produce regression tests you will see soon - without error mentioned above. Apparently boost::noncopyable (or test unit?) got broken somewhere between Aug 18th 06:00 and Aug 18th 12:00 (I do not know what timezone) and this will produce many errors in next regression tests run. Unless it's quickly fixed. B.

2 2