- Boost - lists.boost.org

Building Boost On Tru64
by Eduardo Bezerra 03 Nov '04

03 Nov '04

Hi, I´m trying to build boost_1_31_0 on a Alpha box running Tru64 version 5.1B. After running bjam "-sTOOLS=gcc" stage I get the following error: /usr/include/pthread.h:328:4: #error "Please compile the module including pthread.h with -pthread" Since I´m a newbie to boost I´m looking for some help to handle this issue. Best regards, Eduardo

2 1

Some comments on program_options/howto.html
by Peter Dimov 03 Nov '04

03 Nov '04

I dutifully followed the link from the --no-foo thread, and I have some comments. The Winmain Command Line section says split_command_line in the text, split_winmain in the example code. The Response Files section shows example code for parsing a response file using Tokenizer. Why shouldn't one be able to use split_command_line instead? There doesn't seem to be any difference between a command line in string format and a response file. Also, response file support doesn't seem proper. Response files should work like this: @file1 --option=value @file2 If file1 contains --option, it will be overriden by the command line. Similarly, all options in file2 will override both file1 and the command line --option=value. From a cursory look at the example, this doesn't seem to be the case, but I may be wrong. An additional parser could have been used to enable this behavior if it were possible to return more than one option/value pair from it. (This would also allow "option bundles" like -O1 expanding into a set of option/values.)

2 5

sourceforge open bugs
by Peter Dimov 03 Nov '04

03 Nov '04

We have two pages of open bugs in the sf.net tracker. Many of them are unassigned and it's not clear who should be the assignee since the maintainer is either inactive or does not appear in the "Assigned to" field. I bet we also have many bugs that are resolved but left open - a typical mistake that, in fact, I just made. ;-) -- Peter Dimov http://www.pdimov.com

1 0

minor compile-time issue with boost::regex (1.32)
by Cory Nelson 03 Nov '04

03 Nov '04

this will cause compile warnings in VC7.1 with the "detect 64bit issues" flag set: boost::match_results<string::const_iterator> what; for(boost::match_results<string::const_iterator>::size_type i=0; i<what.size(); i++) results.push_back(string(what[i].first, what[i].second)); warning C4267: 'argument' : conversion from 'size_t' to 'int', possible loss of data it seems the operator takes an int for index instead of size_type. -- Cory Nelson http://www.int64.org

2 3

[Boost-bugs] [ boost-Bugs-1059388 ] shared_ptr::operator-> () const return type should be const
by SourceForge.net 03 Nov '04

03 Nov '04

Bugs item #1059388, was opened at 2004-11-03 13:29 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=1059388&group_… Category: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: Roland (vzaznobin) Assigned to: Peter Dimov (pdimov) Summary: shared_ptr::operator-> () const return type should be const Initial Comment: shared_ptr::operator-> () const return type should be const const T * operator-> () const; T * operator-> (); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1059388&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

RE: [boost] Re: [1.32 Release] Draft tarballs are available
by Michiel Salters 03 Nov '04

03 Nov '04

[offtopic] The "Save As..." dialog is implemented as an explorer dialog, which means you can right-click on the offending file and change the permissions there. Aftert that you can "save as" directly over the original. Works in many windows apps. [/offtopic] -- Michiel Salters. > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org]On Behalf Of Aaron W. > LaFramboise > Sent: maandag 1 november 2004 21:38 > To: boost(a)lists.boost.org > Subject: Re: [boost] Re: [1.32 Release] Draft tarballs are available > > And keep in mind that unlike our Emacs users, not everyone > has an editor > for which overriding read-only attributes is easy. On more than one > occasion have I been trying to edit the read-only source files of some > foolish distribution, remotely in an editor that doesn't > support writing > to read-only files, or shell escapes. Its a real pain, even > on Windows, > to have to manually browse for the offending file and change its > permissions when Notepad spits back some error message about not being > able to save my work. > > Aaron W. LaFramboise > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

1 0

RE: [boost] Re: GUI library - something to think about
by Brian Braatz 03 Nov '04

03 Nov '04

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Hajo Kirchhoff > Sent: Tuesday, November 02, 2004 10:52 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: GUI library - something to think about > > Hello all, > > > Considering the fact that some of the Boosters work on the GUI library, > > I would like to throw something to the mix: > > I wasn't aware that some people here were into GUI work! > > In that case I'd like to gauge interest in my work: > > http://developers.slashdot.org/article.pl?sid=04/10/18/1118242 > > and the homepage at > > http://www.litwindow.com/library > > > This is a two part library. The base part is UI independent while the > second part aims at reducing the work for UI coding. > [Brian Braatz] Wow- that's pretty interesting. Are you considering submitting this for Boost?

2 1

FORMAL review of "Output Formatters" - results
by John Torjo 03 Nov '04

03 Nov '04

Dear all, We got a lot of feedback relating the "Output Formatters" library [1]. "Yes" votes : 4 "No" votes: 2 "Abstain" votes: 2 Conclusions: - The docs and naming of the classes/functions could certainly be improved. - Seems a lot of people want this for pretty output, testing, debugging. - People don't need this library to provide ANY input facilities - quite a few people wanted a redesign. Thus, I wil consider this library "Pending Acceptation". In other words, it's considered Accepted by default, but since it will be redesigned, a new short review will take place. Reece will redesign the library, and a new formal review will take place within 3 months from now. This review will take less time - I assume 7 days. I will talk to Tom and Reece and schedule a next review date. Best, John [1] Just in case you still want a peek at the old code: http://www.torjo.com/code/outfmt.zip (153Kb) -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -- v1.5 - tooltips at your fingertips (work for menus too!) + bitmap buttons (work for MessageBox too!) + tab dialogs, hyper links, lite html

20 54

Tarball testing
by Aleksey Gurtovoy 02 Nov '04

02 Nov '04

Dear regression runners, As we are closing in on the release, I'd like to ask everybody to switch from the release branch to tarball testing. If you are currently using "regression.py", the switch is almost trivial: 1) Download the updated "regression.py" from http://www.meta-comm.com/engineering/boost/regression.py 2) Download the archive of your choice: http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.tar.bz2 http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.tar.gz http://www.meta-comm.com/engineering/boost/200411020208/boost_1_32_0.zip 3) Place the script and the archive in the same directory (e.g. the same one you are currently using for tests on the branch) 4) Modify the script command line to include '--local' option: python regression.py --local=<archive name> [<all other options>] For example, python regression.py --local=boost_1_32_0.zip --runner=metacomm --toolsets=msvc,vc7,vc-7_1,cw-8_3 --pjl-toolset=vc-7_1 5) That's it. If you are using "collect_and_upload_logs.py", simply change '--tag=RC_1_32_0" to "--tag=boost_1_32_0". All test results will be uploaded to ftp://fx.meta-comm.com/boost-regression/boost_1_32_0/, picked up by the reporting tools, and displayed in the usual location -- http://www.meta-comm.com/engineering/boost-regression/developer/index.html. Thank you! -- Aleksey Gurtovoy MetaCommunications Engineering

4 3

Request for data-member smart pointer
by Oleg Fedtchenko 02 Nov '04

02 Nov '04

To Peter Dimov Hi, Peter Could you, please, tell if is there a smart pointer template to a class data-member. I failed to find an appropriate pointer among five ones existing in the boost. I need it for the two tasks appended. By this time, I have written an extension to intrusive_ptr to meet these needs. If you or anyone else are interested I could post it or send in person. Oleg boostoleg(a)yandex.ru Task 1) class A { public: A(){ m_wData = 0;} WORD* GetData(){ return &m_wData} A* CreateA( int nOffset){ return new A;} protected: WORD m_wData; }; main() { A aInstance; WORD* pData = aInstance.CreateA( 15)->GetData(); *pData = 57; // access violation } Task 2) class DocActiveX { protected: Tree* m_pTree; public: ~DocActiveX(){ if(m_pTree) delete m_pTree;} bool Load( const char* lpszPath); Tree* Parse(){ return m_pTree;} }; class DocDirect { protected: Tree* m_pTree; public: ~DocDirect(){ if(m_pTree) delete m_pTree;} bool Load( const char* lpszPath); Tree* Parse(){ return m_pTree;} }; class ShowExternal { public: bool Show( const Tree* pTree); }; class SomeClass { protected: Tree* m_pTree; }; void SomeClass::OnLoad() { DocActiveX* pInstance = new DocActiveX; aInstance.Load( lpszSomePath); m_pTree = aInstance.Parse(); } void SomeClass::OnShow() { ShowExternal ashow; ashow.Show( m_pTree); }

5 19