- Boost - lists.boost.org

[Boost-bugs] [ boost-Bugs-1165980 ] build.sh doesn't build bjam under Solaris by Sun C++
by SourceForge.net 18 Mar '05

18 Mar '05

Bugs item #1165980, was opened at 2005-03-18 17:54 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=1165980&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: simon (atanasyan) Assigned to: Nobody/Anonymous (nobody) Summary: build.sh doesn't build bjam under Solaris by Sun C++ Initial Comment: == Bug description: Boost version: 1.32.0 I work under Solaris 9 and my SunPro compiler is in the unusual place. It looks like boost/tools/build/jam_src/build.sh can't build bjam. % uname -srp SunOS 5.9 sparc % cd boost/tools/build/jam_src % export BOOST_JAM_TOOLSET_ROOT=$HOME/ws//vulcan/dest/sparc-S2/ % /bin/sh -x build.sh BOOST_JAM_TOOLSET= BOOST_JAM_TOOLSET=sunpro + shift BOOST_JAM_OPT_JAM=-o bootstrap/jam0 BOOST_JAM_OPT_MKJAMBASE=-o bootstrap/mkjambase0 BOOST_JAM_OPT_YYACC=-o bootstrap/yyacc0 + test -r /opt/SUNWspro/bin/cc + test -r /cc <<<<<< Error BOOST_JAM_CC=cc == Proposed fix: I attach the patch to this report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1165980&group_… ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[iostreams] Reading a part of file
by Vladimir Prus 18 Mar '05

18 Mar '05

Hello, I wonder if the iostreams library allows me to get an istream that will read a part of a file. That is: I specify a file, start offset and end offset. The resulting istream begins reading at start offset and returns EOF when it arrives at end offset. I haven't found anything like this in the docs and I also don't know if such functionality makes sense for the library. I just need to read individual members of Unix static archives (.a files) and wanted to know if the library can help here. If not, I'll just read the data into strstream. Also: the POSIX mmap call allows one to specify start and end offset. However, the mapped_file_source does not allow to specify that, and documentation does not clearly explain why one would want to use that class at all. TIA, Volodya

2 3

Re: [boost] Re: [ boost-Bugs-1164057 ]boost::filesystem::existshas bugs with UNC paths
by Iain Hanson 18 Mar '05

18 Mar '05

On Thu, 2005-03-17 at 13:51 -0500, Robert Mathews wrote: > "Martin Bonner" <martin.bonner(a)pitechnology.com> wrote in message > news:E562FCEE3A42D61192880002A5FB433302D7A985@kite.pigroup.co.uk... > So, either, we've got to consider "//server" a valid path, or change the > iterator so that it only returns valid paths. I tend to think that fixing > the iterator would be a better choice. > To me, logically, //server is a valid and well formed path. It just so happens that I can't access it ( permission denied ). /ikh

1 0

[Boost-bugs] [ boost-Bugs-1165844 ] С ompilation test/minmax_element_test.cpp failed on Sunpro
by SourceForge.net 18 Mar '05

18 Mar '05

Bugs item #1165844, was opened at 2005-03-18 13:12 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=1165844&group_… Category: test Group: None Status: Open Resolution: None Priority: 5 Submitted By: simon (atanasyan) Assigned to: Beman Dawes (beman_dawes) Summary: Сompilation test/minmax_element_test.cpp failed on Sunpro Initial Comment: = Bug description: Boost version: 1.32.0 Compiler: Sun Studio 10 release (C++ 5.7) with patch 117830-01 % cd ~/boost/libs/algorithm/minmax/test % CC -library=stlport4 -c -library=stlport4 -I/home/sa154628/boost minmax_element_test.cpp minmax_element_test.cpp, line 230: Error: The function "atoi" must have a prototype. 1 Error(s) detected. == Proposed fix Only std c++ headers are included in the minmax_element_test.cpp. Therefore atoi is in the std namespace and isn't exported to global one. So we should change call atoi to std::atoi. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1165844&group_… ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[ptr_container] ptr_map throws in []
by Felipe Magno de Almeida 18 Mar '05

18 Mar '05

Hi. I dont see why ptr_map throws in operator[], I think it should have the same behavior of std::map and return a default constructed object in case it doesnt find the key. Anyway, it is just a opinion. Im using ptr_map in production code and Im obligated to use find to see if the key is already in the map, if it isnt. create one. -- Felipe Magno de Almeida UIN: 2113442 email: felipe.almeida at ic unicamp br, felipe.m.almeida at gmail com, felipe at synergy com I am a C, modern C++, MFC, ODBC, Windows Services, MAPI developer from synergy, and Computer Science student from State University of Campinas(UNICAMP). To know more about: Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br current work: http://www.mintercept.com

2 4

possible optimization to adjacency_list?
by Vikram Shrowty 18 Mar '05

18 Mar '05

Hullo boost gurus, The code at detail/adjacency_list.hpp:1815 is currently like this... remove_vertex_dispatch(Graph& g, vertex_descriptor u, boost::bidirectional_tag) { //.... g.m_vertices.erase(g.m_vertices.begin() + u); //... for (v = 0; v < V; ++v) reindex_edge_list(g.out_edge_list(v), u, edge_parallel_category()); //... If I am understanding this correctly, after erasing a vertex we go through all vertices in the graph and reindex their edges/ This is because there may be edges to/from vertices after u. But this can be avoided if u was the last vertex in the graph, right? So this... //.... g.m_vertices.erase(g.m_vertices.begin() + u); //.... if (u != num_vertices(g)) { //all the re-indexing code } is a valid optimization isn't it? My graph grows and shrinks a lot (but always at highest vertex number) and this code change had a dramatic effect on runtime. -- Vikram Shrowty <vikram(a)lsil.com>

2 1

RE: [boost] [ boost-Bugs-1164057 ]boost::filesystem::exists has b ugs with UNC paths
by Beman Dawes 18 Mar '05

18 Mar '05

At 11:59 AM 3/17/2005, Martin Bonner wrote: >----Original Message---- >From: Robert Mathews [mailto:rmathews@envoyww.com] >Sent: 17 March 2005 14:56 >To: boost(a)lists.boost.org >Subject: [boost] Re: [Boost-bugs] [ boost-Bugs-1164057 >]boost::filesystem::exists has bugs with UNC paths > >>> Initial Comment: >>> boost::filesystem::exists(path("//computer")) always >>> fails, even if the computer exists. > >I shall call this, Issue A. > >>> boost::filesystem::exists(path("//computer/share")) >>> always succeeds, even if the share doesn't exist. > >... and this Issue B. > >> Can anyone actually comment on when or if this bug might actually get >> fixed? It's an obvious bug, the fix is a trivial amount of work - it >> comes with a patch that I've tested on Win32 .... > >Well, as I have indicated above, there are two separate and distinct >issues. Yes. >Issue B does seem like a bug to me. On the other hand, does your fix >change >it so that //computer/printer is reported as a filesystem? That would be a >step backwards. A true return from exists() doesn't make any claim that the path is to a filesystem. Consider this program: #include <iostream> #include <fstream> int main( int argc, char * argv[] ) { std::ofstream os( argv[1] ); if ( !os ) { std::cout << "Could not open " << argv[1] << std::endl; return 1; } os << "Hello, printer!\n"; return 0; } The network name of my machine is "bgd". It has a shared printer named "NECSuper". If I invoke the above program (named "test") like this: >test \\bgd\NECSuper A page gets printed with text: "Hello, printer!" And: >test con: Hello, printer! But: >test \\bgd Could not open \\bgd >test \\bgd\no_such Could not open \\bgd\no_such So I would likewise expect calls to exists("//bgd/NECSuper" ) and exists("con:") to return true, and a call to exists("//bgd/no_such") to return false. My initial feeling about exists("//bgd") is that it should return false, but I'm not very sure about that one and would like to hear more opinions. Thanks for the comments, --Beman

1 0

[logo] what I prefer
by Gennadiy Rozental 17 Mar '05

17 Mar '05

Hi, I wanted to share my thoughts on the logos currently submitted. But first I want to state couple things that IMO worth considering (this is driven my experience, for last release I was tried for month to invent some kind of logo for Boost.Test and obviously failed): 1. IMO logo should be transparent - essentially it should work with most pastel and white colors 2. The shouldn't be border - logo should be natural part of the page 3. No funny fonts - in long run it doesn't work 4. No funny/complex objects - it maybe fun to draw. fun to look first N times, but then it became annoying. This criteria would eliminate a lot of current submissions 6. Logo should be scalable - in a sense that it should work ok in different resolutions 7. There preferable should be something beyond the text - plain text with minimal variations doesn't initiate any recognizability Here couple logos I believe worth considering (This is not an order of my preference): 1. #99 - very solid submission. Look professional, simple. ++ could be used for icon. IMO It bring slogan: boost - blur(beyond,extend, e.t.c) the bounds of C++. May be some extra graphic symbol could be added 2. #10 - simple recognizable, easily scalable (including icon), brings a connotation of ++. Though I would definitely change a colors. May be some extra text are in order 3. #67 Even we kinda agreed that it bring unwanted associations the connotation of building blocks seems good. May be we could reorder'em differently: o o o o o o o ooo or o Also I believe it should be transparent That's about it. Genandiy

8 17

RE: [boost] [ boost-Bugs-1164057 ]boost::filesystem::exists has b ugs with UNC paths
by Martin Bonner 17 Mar '05

17 Mar '05

----Original Message---- From: Robert Mathews [mailto:rmathews@envoyww.com] Sent: 17 March 2005 14:56 To: boost(a)lists.boost.org Subject: [boost] Re: [Boost-bugs] [ boost-Bugs-1164057 ]boost::filesystem::exists has bugs with UNC paths >> Initial Comment: >> boost::filesystem::exists(path("//computer")) always >> fails, even if the computer exists. I shall call this, Issue A. >> boost::filesystem::exists(path("//computer/share")) >> always succeeds, even if the share doesn't exist. ... and this Issue B. > Can anyone actually comment on when or if this bug might actually get > fixed? It's an obvious bug, the fix is a trivial amount of work - it > comes with a patch that I've tested on Win32 .... Well, as I have indicated above, there are two separate and distinct issues. Issue B does seem like a bug to me. On the other hand, does your fix change it so that //computer/printer is reported as a filesystem? That would be a step backwards. Issue A seems correct behaviour to me. A server is *not* a filesystem - it is a place that filesystems can be found. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

function<>::contains
by Peter Dimov 17 Mar '05

17 Mar '05

I added a test case to bind that tests bind objects with function<> and function<>::contains; function<> doesn't have such test cases. In the process I patched the implementation of function<>::contains to work on MSVC 6. However contains_test.cpp will still fail on MSVC 6, because it's misnamed: it mainly tests target() and operator== and I didn't attempt to fix these. I added contains2_test.cpp to the function<> test suite that only tests contains(). It should now pass on MSVC 6. -- Peter "bind (mostly) works on VC 6" Dimov http://www.pdimov.com

2 1