- Boost - lists.boost.org

[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

[tuple] which version to take ?
by Patrick Kowalzick 02 Nov '04

02 Nov '04

Dear all, I am not sure which version of tuples is actual and should be used: -The version in boost/tuple is working and seems consitent to the manual on the boost homepage. -The version in boost/spirit/fusion/sequence is working too and seems to be consistent to "C++ Standard Library Technical Report". tuple_size and tuple_element exist, which do not exist in the first version. Why are there two versions? Which one shall I use? Any recommendations? Thank you, Patrick P.S.: I have another short question, and need a small hint (what to search ;) ) for kind of a "compile time for-loop". Something like this: index[0] = fw_index::template get_index< tuples::tuple_element< 0, TTuple>::type >(); index[1] = fw_index::template get_index< tuples::tuple_element< 1, TTuple>::type >(); ...

6 7

permission problems with latest tar
by Neal D. Becker 02 Nov '04

02 Nov '04

PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc stage ...patience... ...patience... ...found 5608 targets... ...updating 1283 targets... MkDir1 stage mkdir: cannot create directory `stage': Permission denied mkdir "stage" ...failed MkDir1 stage... ...skipped <directory-grist>stage/lib for lack of <directory-grist>stage... MkDir1 bin mkdir: cannot create directory `bin': Permission denied I fixed it by doing: find . -type d | xargs chmod 775

1 1

boost::any
by Dirk Gregorius 02 Nov '04

02 Nov '04

Hi, I have a std::vector<boost::any> m_Processes containing several hydrological processes where a process is implemented like this: template<typename DerivedT> class Process { public: DerivedT& asDerived( void ) { return static_cast<DerivedT&>( *this ); } void Apply( Subbasin& subbasin ) { asDerived().Apply( subbasin ); } } Special Processes are derived from Process and pass their type as template argument ( Barton and Nackman Trick ). I am writing a simulation software for hydrological simulation and want to test if I can get a better performance when getting rid of the virtual function overhead since all types are know at compile time. I want to iterate over all elements of m_Processes in a function void AdvanceTyp( void ). The below implemention doens't work, but will show my intend: template<typename DerivedT> void Subbasin::AdvanceTime( void ) { // Call Process::Apply for each element and pass a *this for_each( m_Processes.begin(), m_Process.end(), bind2nd( mem_func_ref( Process<DerivedT>::Apply, *this ) } At the moment the compiler can't resolve the template argument. How do I have to implement the function, such that it can be resolved by the compiler? -Dirk

2 1

Problems building PDF documentation
by Aleksey Gurtovoy 02 Nov '04

02 Nov '04

While building PDFs for standalone libraries (BB2 is one example) works without a glitch, we were unable to build the master "boost.pdf", due to what appears to be a problem in FOP: ... fop-nt ..\bin.v2\doc\debug\boost.pdf [INFO] FOP 0.20.4 [INFO] building formatting object tree [ERROR] property - "font-selection-strategy" is not implemented yet. [ERROR] property - "line-height-shift-adjustment" is not implemented yet. [ERROR] property - "last-line-end-indent" is not implemented yet. [INFO] [4] [INFO] [5] [INFO] [6] [INFO] [7] [INFO] [8] [INFO] [9] [INFO] [10] [INFO] [11] [INFO] [12] [ERROR] region-name 'xsl-footnote-separator' doesn't exist in the layout-master-set. [ERROR] property - "last-line-end-indent" is not implemented yet. ... [ERROR] property - "last-line-end-indent" is not implemented yet. [INFO] [17] [INFO] [18] [INFO] [19] [INFO] [20] [INFO] [21] [INFO] [22] [ERROR] java.lang.NullPointerException set JAVA_HOME=C:/WINDOWS/system32/java.exe C:/PROGRA~1/FOP-02~1.4/fop.bat ..\bin.v2\doc\debug\boost.fo ..\bin.v2\doc\debug\boost.pdf ...failed fop-nt ..\bin.v2\doc\debug\boost.pdf... ...failed updating 1 target... ...updated 32 targets... This is using: xsltproc --version xsltproc was compiled against libxml 20614, libxslt 10111 and libexslt 809 libxslt 10111 was compiled against libxml 20614 libexslt 809 was compiled against libxml 20614 DocBook XSL 1.66.1 stylesheets FOP 0.20.4/0.20.5 (identical results) on Windows. It's probably possible to get to the root of the issue by commenting out different parts of "doc/src/boost.xml" until it's buildable, but in what little time we could devote to investigating this, we didn't have much success going this route. It would be greatly appreciated if somebody could take a look at this. -- Aleksey Gurtovoy MetaCommunications Engineering

2 2