- Boost - lists.boost.org

Re: [boost] Re: RPC library
by Iain Hanson 07 Mar '05

07 Mar '05

On Sun, 2005-03-06 at 22:59 +0000, Jarl Lindrud wrote: > Iain Hanson <Iain.Hanson <at> videonetworks.com> writes: > To sum up then, your position is that: > > 1) CORBA is the be-all and end-all of distributed programming. > No. Its just the best that we have available. > 2) Anything not projected to need CORBA-style scaleability is just a "toy" and > not worthy of library support. > Probably. But the problem is that people build quick and dirty apps that grow like Topsy. Its the danger of this that make me against non scalable solutions. > > I guess you don't find much need for networking at all in Boost? At least not > beyond lowlevel socket API wrappers and assorted utilites that might be useful > for something like realtime socket apps. Anything beyond that can, and should, > be done with CORBA, regardless of scale and scope. > Doug Schmidt certainly tends to argue in this direction. However, given that CORBA is not ubiquitous and is not ever likely to be then there is always going to be a need for sockets. /ikh

1 0

Help need reed related to libboost_filesystem.lib
by Thota, Vimal 07 Mar '05

07 Mar '05

Dear friends, I am using the boost libraries for my project. When I am compiling the (libboost_filesystem.lib) with my project files libraries which is available in the ibs\filesystem\build\bin\libboost_filesystem.lib\vc7.1\release\runtime-l ink-dynamic , I am facing with the Linking issues which I have listed down. Are you people able to guess where I have gone wrong. Thanks, Vimal Thota Disk Manager error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::dir_it::~dir_it(void)" (??1dir_it@filesystem@boost@@QAE@XZ) Disk Manager error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::dir_it::dir_it(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0dir_it@filesystem@boost@@QAE@ABV?$basic_string@DU?$char_traits@D@std @@V?$allocator@D@2@@std@@@Z) Disk Manager error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::dir_it::dir_it(void)" (??0dir_it@filesystem@boost@@QAE@XZ) Disk Manager error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::get<struct boost::filesystem::is_directory>::operator bool(void)const " (??B?$get@Uis_directory@filesystem@boost@@@filesystem@boost@@QBE_NXZ) Disk Manager error LNK2001: unresolved external symbol "public: class boost::filesystem::dir_it & __thiscall boost::filesystem::dir_it::operator++(void)" (??Edir_it@filesystem@boost@@QAEAAV012@XZ) Disk Manager error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::dir_it::operator*(void)const " (??Ddir_it@filesystem@boost@@QBE?AV?$basic_string@DU?$char_traits@D@std@ @V?$allocator@D@2@@std@@XZ) Disk Manager error LNK2001: unresolved external symbol ___argc Disk Manager error LNK2001: unresolved external symbol ___argv Disk Manager error LNK2001: unresolved external symbol __mbctype Disk Manager error LNK2001: unresolved external symbol __mbctype Disk Manager error LNK2005: "void * __cdecl operator new(unsigned int)" (??2@YAPAXI@Z) already defined in msvcprtd.lib(newop_s.obj) Disk Manager error LNK2005: "void * __cdecl operator new[](unsigned int)" (??_U@YAPAXI@Z) already defined in msvcprtd.lib(newaop_s.obj) Disk Manager error LNK2005: "void __cdecl operator delete(void *)" (??3@YAXPAX@Z) already defined in MSVCRTD.lib(MSVCR71D.dll) Disk Manager error LNK2005: "void __cdecl operator delete[](void *)" (??_V@YAXPAX@Z) already defined in MSVCRTD.lib(MSVCR71D.dll) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::dir_it::~dir_it(void)" (??1dir_it@filesystem@boost@@QAE@XZ) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::dir_it::dir_it(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0dir_it@filesystem@boost@@QAE@ABV?$basic_string@DU?$char_traits@D@std @@V?$allocator@D@2@@std@@@Z) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::dir_it::dir_it(void)" (??0dir_it@filesystem@boost@@QAE@XZ) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::get<struct boost::filesystem::ctime>::operator long const *(void)const " (??B?$get@Uctime@filesystem@boost@@@filesystem@boost@@QBEPBJXZ) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::get<struct boost::filesystem::is_archive>::operator bool(void)const " (??B?$get@Uis_archive@filesystem@boost@@@filesystem@boost@@QBE_NXZ) referenced in function "public: bool __thiscall DirectoryWatcher::next_archived(void)const " (?next_archived@DirectoryWatcher@@QBE_NXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::get<struct boost::filesystem::is_directory>::operator bool(void)const " (??B?$get@Uis_directory@filesystem@boost@@@filesystem@boost@@QBE_NXZ) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall boost::filesystem::get<struct boost::filesystem::mtime>::operator long const *(void)const " (??B?$get@Umtime@filesystem@boost@@@filesystem@boost@@QBEPBJXZ) referenced in function "public: long __thiscall DirectoryWatcher::next_age(void)const " (?next_age@DirectoryWatcher@@QBEJXZ) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall DMWorkflowInterface::~DMWorkflowInterface(void)" (??1DMWorkflowInterface@@QAE@XZ) referenced in function "public: void * __thiscall DMWorkflowInterface::`scalar deleting destructor'(unsigned int)" (??_GDMWorkflowInterface@@QAEPAXI@Z) Disk Manager error LNK2019: unresolved external symbol "public: __thiscall DMWorkflowInterface::DMWorkflowInterface(void)" (??0DMWorkflowInterface@@QAE@XZ) referenced in function "public: virtual void __thiscall DiskManagerService::MainThread(void)" (?MainThread@DiskManagerService@@UAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: bool __thiscall boost::filesystem::dir_it::operator!=(class boost::filesystem::dir_it const &)const " (??9dir_it@filesystem@boost@@QBE_NABV012@@Z) referenced in function "private: void __thiscall DiskManagerService::check_watchers(class std::map<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,class DirectoryWatcher *,struct std::less<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >,class std::allocator<struct std::pair<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const ,class DirectoryWatcher *> > > &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?check_watchers@DiskManagerService@@AAEXAAV?$map@V?$basic_string@DU?$ch ar_traits@D@std@@V?$allocator@D@2@@std@@PAVDirectoryWatcher@@U?$less@V?$ basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@V?$allocat or@U?$pair@$$CBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@ std@@PAVDirectoryWatcher@@@std@@@2@@std@@ABV?$basic_string@DU?$char_trai ts@D@std@@V?$allocator@D@2@@3@@Z) Disk Manager error LNK2019: unresolved external symbol "public: bool __thiscall boost::filesystem::dir_it::operator==(class boost::filesystem::dir_it const &)const " (??8dir_it@filesystem@boost@@QBE_NABV012@@Z) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: class boost::filesystem::dir_it & __thiscall boost::filesystem::dir_it::operator++(void)" (??Edir_it@filesystem@boost@@QAEAAV012@XZ) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: class boost::filesystem::dir_it & __thiscall boost::filesystem::dir_it::operator=(class boost::filesystem::dir_it const &)" (??4dir_it@filesystem@boost@@QAEAAV012@ABV012@@Z) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::dir_it::operator*(void)const " (??Ddir_it@filesystem@boost@@QBE?AV?$basic_string@DU?$char_traits@D@std@ @V?$allocator@D@2@@std@@XZ) referenced in function "private: void __thiscall DirectoryWatcher::find_next(void)" (?find_next@DirectoryWatcher@@AAEXXZ) Disk Manager error LNK2019: unresolved external symbol __mbctype referenced in function "protected: long __thiscall CEditView::OnFindReplaceCmd(unsigned int,long)" (?OnFindReplaceCmd@CEditView@@IAEJIJ@Z) Disk Manager fatal error LNK1120: 17 unresolved externals Disk Manager warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

[optional]output
by Gennadiy Rozental 07 Mar '05

07 Mar '05

Hi, Maybe it's something that I missed, but why optional doesn't define output operator something like this: template<typename T> inline std::ostream& operator<<( std::ostream& ostr, optional<T> const& v ) { if( v ) ostr << *v; return ostr; } Gennadiy

1 0

Boost Logo Contest Request for independent tally
by Joel de Guzman 07 Mar '05

07 Mar '05

Hi, Jonathan noted a minor error in the recent (initial) tally where his entry got listed twice. In the interest of fairness... I would like to request for help. If anyone is interested in doing an independent tally, I'd gladly provide him/her with access to the submitted votes. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

2 2

[congif] BOOST_BEFRIEND_TEMPLATE, BOOST_PRIVATE
by Jonathan Turkanis 07 Mar '05

07 Mar '05

Hi, <boost/shared_ptr.hpp> contains the following in the public section of the class definition (reformatted): // Tasteless as this may seem, making all members public // allows member templates to work in the absence of member // template friends. (Matthew Langston) #ifndef BOOST_NO_MEMBER_TEMPLATE_FRIENDS private: template<class Y> friend class shared_ptr; template<class Y> friend class weak_ptr; #endif T * px; // contained pointer detail::shared_count pn; // reference counter This has become a pretty common technique, I believe. I certainly use it a lot, at any rate. I'd like to suggest two macros which would allow code like the above to be simplified as follows: BOOST_PRIVATE: BOOST_BEFRIEND_TEMPLATE(shared_ptr, Y, 1) BOOST_BEFRIEND_TEMPLATE(weak_ptr, Y, 1) T * px; // contained pointer detail::shared_count pn; // reference counter Here BOOST_PRIVATE would expand to "private" for compilers that support template friends and to "public" otherwise; BOOST_BEFRIEND_TEMPLATE would expand to a template friend declaration where supported, and to nothing otherwise. It might be desirable to have two macros BOOST_BEFRIEND_TEMPLATE_CLASS and BOOST_BEFRIEND_TEMPLATE_STRUCT to avoid compiler warnings. Jonathan

3 9

Logo Contest: Send In Your votes!
by Joel de Guzman 07 Mar '05

07 Mar '05

Hi Y'all, Acceptance of logo entries is officially over. I waited more than 24 hours after the March 1 deadline to account for the time zones. For my convenience, I find it best to simply collect the votes by email. For this purpose, I setup a mail account at address: boost.logo.contest(a)gmail.com where you can send your votes to. For transparency, I shared the password with the Boost Moderators, so they can check the status anytime. Please be reminded that voting shall be based on Instant Runoff Voting (http://www.fairvote.org/irv/whatis2.htm) meaning that each individual voter shall choose 5 favorites, in order of preference. Please send in your votes in this format: 1. 1st choice: Entry number (variant), Submitter 2. 2nd choice: Entry number (variant), Submitter 3. 3rd choice: Entry number (variant), Submitter 4. 4th choice: Entry number (variant), Submitter 5. 5th choice: Entry number (variant), Submitter ***where variant, designated by a letter, is optional. Example: 1. 225, John Doe 2. 336a, Jane Doe 3. 751, Apple Pie 4. 101b, Dorothy Rainbow 5. 855, Kim Possible I shall be collecting votes and progressively posting the results in the boost web site. The competition will close on March 15, 2005 and the winning entry will be announced soon thereafter. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

5 12

RE: [boost] high_resolution_timer \ timer feature requests forBoost.Timer
by Brian Braatz 07 Mar '05

07 Mar '05

(sorry - mail client weirdness on the last post- I have fixed the doublespacing)(here is the mail again) ********************************************* First off- note that Timer can take a start time on the ctor: class timer { public: timer() { _start_time = std::clock(); } // postcondition: elapsed()==0 (snip) high_resolution_timer does not however: class high_resolution_timer { public: // ctor high_resolution_timer() { start_time.QuadPart = 0; frequency.QuadPart = 0; if (!QueryPerformanceFrequency(&frequency)) throw std::runtime_error("Couldn't acquire frequency"); restart(); } (snip) MY PROBLEM: I need to feed the timer the START time (or get FROM it the start time would be preferred) The reason I need this is because for logging purposes (working with the Profiler from Christopher Diggins) I need to log the start and stop times, and I need it to (for internal cross reference) be the same number for multiple purposes. MY REQUESTS: Easy request: high_resolution_timer is changed to have the same type of ctor as timer does May Start a discussion request: That something like a starttime() method is provided for both classes Medium request- That both classes do a typedef for the type returned by the starttime method i.e. instead of class high_resolution_timer { public: (snip) private: timer t; // backup in case of QueryPerformanceCounter() bug LARGE_INTEGER start_time; LARGE_INTEGER frequency; }; You have instead: class high_resolution_timer { public: (snip) typedef LARGE_INTEGER TIME_TYPE; private: timer t; // backup in case of QueryPerformanceCounter() bug TIME_TYPE start_time; TIME_TYPE frequency; }; (for both high_resolution_timer and timer) There you go, those are my requests. Now I will sit here quietly and hope there is a Santa Claus.... (grin)

3 2

RE: [boost] Re: high_resolution_timer \ timer feature requestsforBoost.Timer
by Brian Braatz 06 Mar '05

06 Mar '05

The code I am using was originally developed by Christopher Diggins. His code allows for use of boost.timer or the high_resolution_timer. I am currently using the high_resolution timer. THANK YOU for the suggestion of using the microsec_time_clock.hpp. I did not know that existed, do you know how does this compare to the high_resolution timer? I need to stick to a base release version of boost for production reasons, do you think this other timer will work inside 1.32? Thank you very much for your thoughts, I would not have noticed the microsec if you had not pointed it out to me. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Caleb Epstein > Sent: Friday, March 04, 2005 8:32 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] Re: high_resolution_timer \ timer feature > requestsforBoost.Timer > > On Fri, 4 Mar 2005 10:42:16 -0700, Brian Braatz <brianb(a)rmtg.com> wrote: > > > But the Profile LOG (like a trace of what happened) looks like this > > DEPTH NAME TIME > > 0 FuncA 2 Seconds > > 1 FuncB 1 Second > > > > Does that answer your question, or am I missing something? > > Just a subtle point, but the boost::timer class returns CPU time used > not elapsed wall-clock time and would return results of ~0.0 for a > function that just sleep'd for a second or two. > > If what you're looking for is a high-resolution clock, try > <boost/date_time/microsec_time_clock.hpp> (at least in the latest > CVS). If you want performance or profiling information, use > boost::timer. > > > -- > Caleb Epstein > caleb dot epstein at gmail dot com > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Integrating Boost Documentation with Visual Studio IDE.
by Pavel Chikulaev 06 Mar '05

06 Mar '05

Hi all, I don't know how many of boosters use VC, but I think intergrating boost documentation with visual studio IDE will help VC developers a lot. Key feature is context help, for example pressing F1 when cursor is on "BOOST_PP_REPEAT" token will instantly open help on BOOST_PP_REPEAT instead of opening boost.org(or saved page), then documentation, then preprocessor, the reference, then scrolling a lot in left frame for PP_REPEAT. Right know I don't know how to do it, but I'll try to find the easiest way to do it. P.S. I almost have no exprerience with other IDEs, but I think it is also possible to integrate boost documentation with them too.

2 1

Wanted : Modified Boost Jamfiles for Mac OS X
by Tommy Nordgren 06 Mar '05

06 Mar '05

Could someone please mail me an archive with modified Jamfiles, that allows the Boost 1.32 libraries to be built with Mac OS X 10.3.8, on a 512 MB machine. Currently the build stalls when compiling a file called xml_parser.cpp, exhausting virtual memory. As an alternative, can someone tell me how to exclude builds that uses the Spirit Framework. "Home is not where you are born, but where your heart finds peace" - Tommy Nordgren, "The dying old crone"

4 3