- Boost-users - lists.preview.boost.org

New design proposal for boost::filesystem
by Carlo Wood 20 Aug '04

20 Aug '04

I propose the following design. The aim of boost::filesystem should be to support the following coding idiom: * The programmer should take care to only handle two types of paths in his application: 1) Complete paths 2) Relative paths * The programmer will have to specifically tell the libary when a constructed path is 'native' and when not. A native path is accepted according to native rules and never gives any problem (exceptions) further on. A non-native path is checked … [View More]according to the existing rules, which basically means that the programmer can set a default check routine that will in effect determine how portable the application will be. I propose two design changes: 1) 'native' is now not only a representation, but an *internal state* of fs::path. (this has no effect on the representation as returned by fs::path::string()). 2) All 'complete' paths are automatically marked as 'native'. Examples, the following code is legal: fs::path p1("C:\foo\a.exe", native); // Fails on linux, success on windows. fs::path p2("/usr/src/a.out, native); // Fails on windows, success on linux. std::cout << p1.native_file_string(); // ok, p1 is native. fs::path p3("foo/bar"); // Relative path, always succeeds. std::cout << p.string(); // ok std::cout << p.native_directory_string(); // Useless, but ok. fs::path p4(complete(p3)); // p4 is now "native", because now it is complete. std::cout << p4.native_directory_string(); // ok And the following will throw: std::cout << p4.string() // Not allowed because p4 is native (complete). Since there would be a default way defined of how a relative path is completed, all operation functions will accept both, relative and complete paths. For example: fs::path p1("C:\cygwin\usr/bin/ls", native); // Legal path on Cygwin. if (fs::exists(p1)) // Ok, access complete path. // For clarification fs::path p2("C:\cygwin\usr"); // Just an example fs::default_working_directory(p2); // fictuous function. fs::path p3("bin/ls"); // Portable representation (refers in fact to "C:\cygwin\usr\bin\ls.exe"). if (fs::exists(p3)) // Ok : exists() will make the path complete before testing. And this throws: fs::path p4("/bin/ls"); // Not allowed: this path has a root but is not marked 'native'. Setting the default_working_directory shall allways need to be done for each supported OS seperately. Of course you can set it to "/" on single root machines, and set it to "E:/" after extracting the 'E:' from the current path at application start up, in effect simulating a 'single root': int main() { fs::default_working_directory(fs::current_path().root_path()); // ... simulate single root machine below. fs::path p("bin/ls"); } The average application will work with relative paths, relative to some (native) base directory and next to that have some arbitrary, complete and thus native directories (ie, read from environment variables). But in case more than one 'working' directory seems needed then we can add support for that too by allowing to construct paths with a reference to the (complete/native) working directory. Ie, fs::path home_base(...); // ... fs::path runtime_rcfile(home_base); // ... runtime_rcfile = "myapplication/config/runtime/rc"; which is then relative to `home_base' instead of a single, global 'working directory' (as now returned by fs::current_path()). Most of the current boost::filesystem API can be preserved with this design. -- Carlo Wood <carlo(a)alinoe.com> [View Less]

1 0

Question about static linking of boost
by Daniel Huber 20 Aug '04

20 Aug '04

Thanks to Stephen for helping me get my boost to link. I feel bad for not thinking of this solution myself. I have one final question/suggestion about the getting started document (which I found to be very well written). I compile and install boost using the following command: tools/build/jam_src/bin.linuxx86/bjam "-sTOOLS=gcc" "-sBUILD=release <runtime-link>static" --prefix=$HOME/linux/lib/boost install My goal was to create a minimal set of boost libraries (basically, I just … [View More]

2 1

Using boost::date_time for timezones
by Duncan Woods 19 Aug '04

19 Aug '04

Hello All, I'm new to Boost and interested in using it for timezone conversions but I'm not finding it terribly clear. An example, which works fine, uses something of the form: typedef boost::date_time::local_adjustor<ptime, -5, us_dst> us_eastern; 1. My problem is that I wish to use DST settings other than US and found definitions such as eu_dst_trait in local_timezone_defs.hpp but these seem unused and unusable. Would it require implementation of dst_rules.hpp type classes? If … [View More]

2 4

Inter Process Communication lib?
by Fernando Cacciola 19 Aug '04

19 Aug '04

Just a silly question... none of the boost libs provides cross platform IPC right? Txs Fernando Cacciola SciSoft

2 2

File size and attributes
by Surya Kiran Gullapalli 19 Aug '04

19 Aug '04

Hi all, I'm new to Boost library, working with boost-1.31.0. I'm trying to find out the size of the file and its attributes (hidden, readonly etc) using boost filesystem library. I had a go at the documentation, but did not get much help. Thanks in advance, Surya

1 0

mpl::switch question
by Istvan Buki 18 Aug '04

18 Aug '04

Hello, I've just tried to compile a small piece of code using mpl::switch_ starting from an example Aleksey Gurtovoy sent to this list a while ago. I slightly modified the code to use the boost::is_same<T,U> template but I can't make it compile. On the other hand, if I comment out the line in the switch_body containing the is_same template, it compile without any problem. I spent the whole day on this and I'm lost. Any help would be welcome. Thanks, Istvan PS: I'm using boost 1.… [View More]

1 0

RE: [Boost-users] regex: match_results::const_reference is someti messub_match<Bidi Iterator>, sometimes const char?
by Richard Reitmeyer 17 Aug '04

17 Aug '04

Thanks for your help. (And all the effort that went into the regex library.) I'm using 1.31.0 (unpatched). After a more careful examination, my problem was that I was passing the wrong kind of allocator as a template parameter. Richard > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of John Maddock > Sent: Tuesday, August 17, 2004 5:33 AM > To: boost-users(a)lists.boost.org > Subject: Re:… [View More]

1 0

BGL-kamada_kawai_spring_layout
by Gordon Smith 17 Aug '04

17 Aug '04

Just playing with the kamada_kawai_spring_layout, so far for any non trivial graph (more then 4 nodes) - it seems to just go into an infinite loop. The graph is undirected but would contain "circular" paths - thoughts? Gordon.

1 0

Additional information on linking problems
by Daniel Huber 17 Aug '04

17 Aug '04

Hi, I have done some additional testing on th eproblem that I reported yesterday, and I have found that the problem I was having with static linking under gcc 2.95.3 also occurs on gcc 3.2.2. I get basically the same error message (see below). I guess that the reason I get the message for the static linking but not for the dynamic linking might be that the undefined references in a shared library are ok as long as those functions are not called. Is that correct? I looked at the code, … [View More]and as far as I can tell, the functions that the compiler is complaining about are in fact defined. Does anyone have any suggestions? Thanks, Daniel g++ -L $HOME/linux/lib/boost/lib -static -lboost_filesystem -gcc -I $HOME/linux/lib/boost/include/boost-1_31 test_boost.cxx /tmp/ccP4gcx3.o(.text+0x19): In function `main': : undefined reference to `boost::filesystem::initial_path()' /tmp/ccP4gcx3.o(.text+0x3e): In function `main': : undefined reference to `boost::filesystem::native(std::basic_string<char, std: :char_traits<char>, std::allocator<char> > const&)' /tmp/ccP4gcx3.o(.text+0x4f): In function `main': : undefined reference to `boost::filesystem::path::path[in-charge](char const*, bool (*)(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&))' /tmp/ccP4gcx3.o(.text+0x5f): In function `main': : undefined reference to `boost::filesystem::system_complete(boost::filesystem:: path const&)' /tmp/ccP4gcx3.o(.text+0x114): In function `main': : undefined reference to `boost::filesystem::exists(boost::filesystem::path cons t&)' /tmp/ccP4gcx3.o(.text+0x137): In function `main': : undefined reference to `boost::filesystem::path::native_file_string() const' /tmp/ccP4gcx3.o(.text+0x1ba): In function `main': : undefined reference to `boost::filesystem::is_directory(boost::filesystem::pat h const&)' /tmp/ccP4gcx3.o(.text+0x1dd): In function `main': : undefined reference to `boost::filesystem::path::native_directory_string() con st' /tmp/ccP4gcx3.o(.text+0x28c): In function `main': : undefined reference to `boost::filesystem::is_directory(boost::filesystem::pat h const&)' /tmp/ccP4gcx3.o(.text+0x2c0): In function `main': : undefined reference to `boost::filesystem::path::leaf() const' /tmp/ccP4gcx3.o(.text+0x342): In function `main': : undefined reference to `boost::filesystem::path::leaf() const' /tmp/ccP4gcx3.o(.text+0x404): In function `main': : undefined reference to `boost::filesystem::path::leaf() const' /tmp/ccP4gcx3.o(.text+0x572): In function `main': : undefined reference to `boost::filesystem::path::native_file_string() const' /tmp/ccP4gcx3.o(.gnu.linkonce.t._ZN5boost10filesystem18directory_iteratorC1ERKNS 0_4pathE+0x1f): In function `boost::filesystem::directory_iterator::directory_it erator[in-charge](boost::filesystem::path const&)': : undefined reference to `boost::filesystem::detail::dir_itr_init(boost::shared_ ptr<boost::filesystem::detail::dir_itr_imp>&, boost::filesystem::path const&)' /tmp/ccP4gcx3.o(.gnu.linkonce.t._ZNK5boost10filesystem18directory_iterator11dere ferenceEv+0xd): In function `boost::filesystem::directory_iterator::dereference( ) const': : undefined reference to `boost::filesystem::detail::dir_itr_dereference(boost:: shared_ptr<boost::filesystem::detail::dir_itr_imp> const&)' /tmp/ccP4gcx3.o(.gnu.linkonce.t._ZN5boost10filesystem18directory_iterator9increm entEv+0xd): In function `boost::filesystem::directory_iterator::increment()': : undefined reference to `boost::filesystem::detail::dir_itr_increment(boost::sh ared_ptr<boost::filesystem::detail::dir_itr_imp>&)' collect2: ld returned 1 exit status [View Less]

2 1

regex: match_results::const_reference is sometimes sub_match<Bidi Iterator>, sometimes const char?
by Richard Reitmeyer 17 Aug '04

17 Aug '04

Hello, all. The regex library is extremely helpful: thanks for all your efforts. I've got a problem with gcc and stlport and boost: when I try to get a submatch on other platforms, I can take my match object, m, and do things like m[n].str(); // works great elsewhere But with gcc / stlport, with BOOST_NO_STD_ALLOCATOR not defined, the const_reference type is defined as Allocator::const_reference (which is `const char'), rather than sub_match<BidiIterator>. So operator[] gives me a … [View More]

2 1

minimal use of strong_components
by Michael W Daniels 16 Aug '04

16 Aug '04

boost 1.31.0, msvc 7.1 I'm trying to understand how to use the BGL and the strong_components algorithm in particular. From the example in the documentation, it seems like this minimal file should compile: ==test.cpp== #include <boost/graph/adjacency_list.hpp> #include <boost/graph/strong_components.hpp> #include <string> using namespace std; using namespace boost; typedef adjacency_list<setS, setS, bidirectionalS, property<vertex_name_t, string> > Graph; … [View More]int testcomps() { Graph gramgraph; vector<int> component(num_vertices(gramgraph)); return strong_components(gramgraph, &component[0]); } ==end== Instead, I get the error below. It seems as though it doesn't like the component map type, but I don't know what I should use instead. Any help anyone could provide would be appreciated. ==error== Compiling... test.cpp e:\boost-msvc\include\boost-1_31\boost\property_map.hpp(159) : error C2664: 'const T &get<std::allocator<_Ty>::value_type>(const T *,ptrdiff_t)' : cannot convert parameter 2 from 'Vertex ' to 'ptrdiff_t' with [ T=std::allocator<int>::value_type, _Ty=int ] This conversion requires a reinterpret_cast, a C-style cast or function-style cast e:\boost-msvc\include\boost-1_31\boost\property_map.hpp(156) : while compiling class-template member function 'void boost::ReadablePropertyMapConcept<PMap,Key>::constraints(void)' with [ PMap=int *__w64 , Key=Vertex ] e:\boost-msvc\include\boost-1_31\boost\concept_check.hpp(49) : see reference to class template instantiation 'boost::ReadablePropertyMapConcept<PMap,Key>' being compiled with [ PMap=int *__w64 , Key=Vertex ] e:\boost-msvc\include\boost-1_31\boost\property_map.hpp(215) : see reference to function template instantiation 'void boost::function_requires<boost::ReadablePropertyMapConcept<PMap,Key>>(boost::mpl::identity<T> *)' being compiled with [ PMap=int *__w64 , Key=Vertex , T=boost::ReadablePropertyMapConcept<int *__w64 ,Vertex > ] e:\boost-msvc\include\boost-1_31\boost\property_map.hpp(214) : while compiling class-template member function 'void boost::ReadWritePropertyMapConcept<PMap,Key>::constraints(void)' with [ PMap=int *__w64 , Key=Vertex ] e:\boost-msvc\include\boost-1_31\boost\concept_check.hpp(49) : see reference to class template instantiation 'boost::ReadWritePropertyMapConcept<PMap,Key>' being compiled with [ PMap=int *__w64 , Key=Vertex ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(111) : see reference to function template instantiation 'void boost::function_requires<boost::ReadWritePropertyMapConcept<PMap,Key>>(boost::mpl::identity<T> *)' being compiled with [ PMap=int *__w64 , Key=Vertex, T=boost::ReadWritePropertyMapConcept<int *__w64 ,Vertex> ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(166) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::detail::strong_components_impl<Graph,ComponentMap,RootMap,boost::iterator_property_map<RandomAccessIterator,IndexMap,T,R>,int,int,boost::no_property>(const Graph &,ComponentMap,RootMap,DiscoverTime,const boost::bgl_named_params<int,Tag> &)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 , RootMap=boost::iterator_property_map<std::vector<Vertex>::iterator,boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr RootMap=boost::iterator_property_map<std::vector<Vertex>::iterator,boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type & >, RandomAccessIterator=std::vector<size_type>::iterator, IndexMap=boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type, T=std::allocator<size_type>::value_type, R=std::allocator<size_type>::value_type &, DiscoverTime=boost::iterator_property_map<std::vector<size_type>::iterator,boost::detail::choose_pmap_helper<boost::property_value< boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type,std::allocator<size_type>::value_type,std::allocator<size_type>::value_type &>, Tag=int ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(179) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::detail::strong_comp_dispatch2<boost::detail::error_property_not_found>::apply<Graph,ComponentMap,RootMap,int,int,boost::no_property>(const Graph &,ComponentMap,RootMap,const boost::bgl_named_params<T,Tag> &,boost::detail::error_property_not_found)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 , RootMap=boost::iterator_property_map<std::vector<Vertex>::iterator,boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr RootMap=boost::iterator_property_map<std::vector<Vertex>::iterator,boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type & >, T=int, Tag=int ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(216) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::detail::scc_helper2<Graph,ComponentMap,boost::iterator_property_map<RandomAccessIterator,IndexMap,T,R>,int,int,boost::no_property,boost::property_value<PropertyList,Tag>::type>(const Graph &,ComponentMap,RootMap,const boost::bgl_named_params<int,int> &,DiscoverTimeMap)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 , RandomAccessIterator=std::vector<Vertex>::iterator, IndexMap=boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type, T=std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr T=std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type, R=std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr R=std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type & , PropertyList=boost::bgl_named_params<int,int>, Tag=boost::vertex_discover_time_t, RootMap=boost::iterator_property_map<std::vector<Vertex>::iterator,boost::detail::choose_pmap_helper<boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_index_t>::type,Graph,boost::vertex_index_t>::const_result_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,b oost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type,std::allocator<boost::detail::adj_list_gen<boost::adjacency_list<boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>>,boost::setS,boost::setS,boost::bidirectionalS,boost::property<boost::vertex_name_t,std::string>,boost::no_property,boost::no_property,boost::listS>::config::vertex_ptr >::value_type & >, DiscoverTimeMap=boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_discover_time_t>::type ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(229) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::detail::strong_comp_dispatch1<boost::detail::error_property_not_found>::apply<Graph,ComponentMap,int,int,boost::no_property>(const Graph &,ComponentMap,const boost::bgl_named_params<T,Tag> &,boost::detail::error_property_not_found)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 , T=int, Tag=int ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(243) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::detail::scc_helper1<Graph,ComponentMap,boost::property_value<PropertyList,Tag>::type,int,int,boost::no_property>(const Graph &,ComponentMap,const boost::bgl_named_params<T,int> &,RootMap)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 , PropertyList=boost::bgl_named_params<int,int>, Tag=boost::vertex_root_t, T=int, RootMap=boost::property_value<boost::bgl_named_params<int,int>,boost::vertex_root_t>::type ] e:\boost-msvc\include\boost-1_31\boost\graph\strong_components.hpp(253) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::strong_components<Graph,ComponentMap,int,int,boost::no_property>(const Graph &,ComponentMap,const boost::bgl_named_params<T,Tag> &)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 , T=int, Tag=int ] e:\Projects\gidlp\parser\test.cpp(13) : see reference to function template instantiation 'boost::property_traits<PA>::value_type boost::strong_components<Graph,std::allocator<_Ty>::value_type*__w64 >(const Graph &,ComponentMap)' being compiled with [ PA=std::allocator<int>::value_type *__w64 , _Ty=int, Graph=Graph, ComponentMap=std::allocator<int>::value_type *__w64 ] ==end== [View Less]

1 0

RTTI for VC 6
by Samuel 16 Aug '04

16 Aug '04

VC 6 has an option for Run-Time Type Information (RTTI) that is normally off. I was able to compile and execute a sample program that had a problem. I noticed that Boost uses RTTI (such as the dynamic_cast operator), so I checked to see if the option was on; it was not. I turned the option on and the program worked. That problem is probably a known problem, but something such as the following can be added somewhere to not allow a VC 6 program to even compile if the RTTI option is off. I think … [View More]

6 22

Re: [Boost-users] Re: RTTI for VC 6
by Samuel 16 Aug '04

16 Aug '04

[The message I am replying to was sent from a newsgroup and I am sending my reply (this) as a message to the list.] "Edward Diener" <eddielee(a)tropicsoft.com> wrote in message news:cfmhi0$4fd$1@sea.gmane.org... > > What Mr. Dimov is saying is that it is impossible to place the code you > would like to use above in Boost because it would affect other Boost > libraries which do not need RTTI to work. That's no problem. The Boost headers already have more than 400 (including … [View More]

2 2

RE: [Boost-users] RTTI for VC 6
by Bjorn.Karlsson＠readsoft.com 16 Aug '04

16 Aug '04

Enough of this. There will be no more insults, and no more blame, in this thread. Please try again, in a more productive manner. Thanks, Bjorn Karlsson Moderator [Everything snipped]

1 0

Boost.Python 'Fatal Error'
by Ed Fear 16 Aug '04

16 Aug '04

Hello there, I've just started using Boost.Python, and find it absolutely invaluable. For the moment, my main task is embedding the python interpreter within an application of mine, and I have successfully built a small application that can load a module, execute a Python function and then collect the result. The next logical step was to extend the Python script somewhat into objects. I wrote some extra code in the script which I checked with the command line interpreter and verified to … [View More]

2 1

polymorphic container/boost::any
by goochrules! 16 Aug '04

16 Aug '04

I'm quite sure that this problem has been addressed many times before, so I suspect it as a better name and I suspect that boost::any could be the solution. I want to store related types in the same stl container, for instance, this is the class heirachy I want: class tree { public: void grow() =0; }; class oak : public tree { public: void grow() { std::cout << "oak grows slowly" << std::endl; }; class pine : public tree { public: void grow() { std::cout << "pine grows … [View More]

4 6

problem with static linking on linux gcc 2.95.3
by Daniel Huber 16 Aug '04

16 Aug '04

Hi, I am wondering if any of you boost gurus can help with this problem. I have compiled and installed boost using gcc 2.95.3 on a linux redhat 7 machine. The install actually fails on some targets. I get this message at the end of the install: ...failed updating 24 targets... ...skipped 48 targets... ...updated 2343 targets... But I am guessing that this is expected behavior for an old compiler. Anyway, I am interested in the filesystem library at this time, and so I tried compiling … [View More]the simple_ls.cpp example. When I compile using the default linking (which uses shared objects), the program works fine, but when I compile using the -static flag to limit to static linking, I get a lot of undefined reference errors (see below). Unfortunately, I haven't been able to figure out why this would happen. Any suggestions on how to debug this or as to what might be going wrong would be greatly appreciated. Sincerely, Daniel /tmp/ccU0ehTU.o: In function `main': /tmp/ccU0ehTU.o(.text+0xc): undefined reference to `boost::filesystem::initial_path(void)' /tmp/ccU0ehTU.o(.text+0x2c): undefined reference to `boost::filesystem::native(basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> > const &)' /tmp/ccU0ehTU.o(.text+0x3e): undefined reference to `boost::filesystem::path::path(char const *, bool (*)(basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> > const &))' /tmp/ccU0ehTU.o(.text+0x50): undefined reference to `boost::filesystem::system_complete(boost::filesystem::path const &)' /tmp/ccU0ehTU.o(.text+0xe8): undefined reference to `boost::filesystem::exists(boost::filesystem::path const &)' /tmp/ccU0ehTU.o(.text+0x10d): undefined reference to `boost::filesystem::path::native_file_string(void) const' /tmp/ccU0ehTU.o(.text+0x188): undefined reference to `boost::filesystem::is_directory(boost::filesystem::path const &)' /tmp/ccU0ehTU.o(.text+0x1ad): undefined reference to `boost::filesystem::path::native_directory_string(void) const' /tmp/ccU0ehTU.o(.text+0x257): undefined reference to `boost::filesystem::is_directory(boost::filesystem::path const &)' /tmp/ccU0ehTU.o(.text+0x289): undefined reference to `boost::filesystem::path::leaf(void) const' /tmp/ccU0ehTU.o(.text+0x2f5): undefined reference to `boost::filesystem::path::leaf(void) const' /tmp/ccU0ehTU.o(.text+0x427): undefined reference to `boost::filesystem::path::native_file_string(void) const' /tmp/ccU0ehTU.o(.text+0x5ab): undefined reference to `boost::filesystem::path::leaf(void) const' /tmp/ccU0ehTU.o: In function `boost::filesystem::directory_iterator::directory_iterator(boost::filesystem::path const &)': /tmp/ccU0ehTU.o(.boost::filesystem::directory_iterator::gnu.linkonce.t.(boost::filesystem::path const &)+0x26): undefined reference to `boost::filesystem::detail::dir_itr_init(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp> &, boost::filesystem::path const &)' /tmp/ccU0ehTU.o: In function `boost::filesystem::directory_iterator::dereference(void) const': /tmp/ccU0ehTU.o(.boost::filesystem::directory_iterator::gnu.linkonce.t.dereference(void) const+0x12): undefined reference to `boost::filesystem::detail::dir_itr_dereference(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp> const &)' /tmp/ccU0ehTU.o: In function `boost::filesystem::directory_iterator::increment(void)': /tmp/ccU0ehTU.o(.boost::filesystem::directory_iterator::gnu.linkonce.t.increment(void)+0x12): undefined reference to `boost::filesystem::detail::dir_itr_increment(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp> &)' collect2: ld returned 1 exit status [View Less]

1 0

Re:Re: Regex help needed, please help
by Kosta Adarchenko 16 Aug '04

16 Aug '04

Message: 8 Date: Sun, 15 Aug 2004 10:31:50 +0100 From: "John Maddock" <john(a)johnmaddock.co.uk> Subject: Re: [Boost-users] Regex help needed, please help. To: <boost-users(a)lists.boost.org> Message-ID: <00a601c482ab$78c9dc10$d8ec0352@fuji> Content-Type: text/plain; charset="iso-8859-1" > John, I have stated the exact regex, it's \d\d\d\d\d\d , a simple regex matching 6 numbers, but the same happens even with one \d regex. I don't see a way to refactor the \d expression.… [View More]

1 0

Regex help needed, please help.
by Kosta Adarchenko 15 Aug '04

15 Aug '04

boost-users-request(a)lists.boost.org wrote: Send Boost-users mailing list submissions to boost-users(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit http://www.lists.boost.org/mailman/listinfo.cgi/boost-users or, via email, send a message with subject or body 'help' to boost-users-request(a)lists.boost.org You can reach the person managing the list at boost-users-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: … [View More]Contents of Boost-users digest..." Today's Topics: 1. Re: Regex problems, please help (John Maddock) ---------------------------------------------------------------------- Message: 1 Date: Fri, 13 Aug 2004 11:39:54 +0100 From: "John Maddock" Subject: Re: [Boost-users] Regex problems, please help To: Message-ID: <01d401c48125$ee4e79f0$3c520352@fuji> Content-Type: text/plain; charset="iso-8859-1" > After some seven thousands hits the match algo throughs the memory exhausted exception. > So I cought the exception and moved the iterator by one, printed the location it points to in my searched file to view the problematic section for the regex find algorithm. > I have noticed that the problem happens not with all large files, but with quite a bit of them. > After I have received the problematic section in my file, I ran the program on it and it did not raise any exceptions. > Please , help me I have a Graduate project to complete within 3 weeks from now, and this is one of the major bugs I have not resolved. You don't say *exactly* what the regex is that's causing the problem - it makes a difference - problems like this are usually caused by an expression that behaves badly with specific input (because regexes are NP-Hard to match in the general case). Boost.Regex will throw an exception rather than go on thrashing forever trying to find a match, but to determine whether this is the case here, you need to trap the exception at the point it's being thrown, and see if the regex lib is indeed the culprit, if it is, then refactoring the expression that you're using so that it's less ambiguous is usually the answer. John. ------------------------------ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://www.lists.boost.org/mailman/listinfo.cgi/boost-users End of Boost-users Digest, Vol 279, Issue 2 ******************************************* John, I have stated the exact regex, it's \d\d\d\d\d\d , a simple regex matching 6 numbers, but the same happens even with one \d regex. I don't see a way to refactor the \d expression. --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! [View Less]

2 1

[boost-users]_BGL:_copy_component_bugs
by Erik Jenelius 13 Aug '04

13 Aug '04

Hi. In boost/graph/copy.hpp, besides the copy_graph function, I noticed a nice, undocumented function called copy_component which uses breadth-first search to copy a component from a graph to a new graph. Unfortunately, it doesn't work. I think there are at least two bugs in it: 1. The vertices are copied at the examine_vertex event point and the edges are copied at the examine_edge event point. However, the target of the edge has not yet been examined at that point, which leads to strange … [View More]

1 0

Regex problems, please help
by Kosta Adarchenko 13 Aug '04

13 Aug '04

Here is the problem: I want to find a simple regular _expression something like \\d\\d\\d\\d\\d\\d in a large file (15 mb) using VC++ 7.1 . I use Spirit's File Iterator as the input iterator for the search algorithm. After some seven thousands hits the match algo throughs the memory exhausted exception. So I cought the exception and moved the iterator by one, printed the location it points to in my searched file to view the problematic section for the regex find algorithm. After the "… [View More]problematic section" of some 300 chars ends the algorithm keeps working fine. here is the code. //------------------------------------------------------------------------------------------- void TheFunction() { //print the problematic section here ofstream of; of.open("d:\\err1.txt"); boost::spirit::file_iterator< > begin("d:\\log1.txt"); boost::spirit::file_iterator<> beginning_saved(begin); //save the beginning in order to compare later boost::spirit::file_iterator< > ending; ending= begin.make_end(); boost::match_results<boost::spirit::file_iterator<char > > what; boost::match_flag_type flags = boost::match_default; long matchescounter=0; std::exception e; int i; bool found; found=false; try { found=boost::regex_search(begin, ending, what, _expression, flags); if (found) { begin =what[0].second; cout<<what[0]; matchescounter=1; } } catch (std::exception &e) { cout<<e.what(); } while(found) { try { found=boost::regex_search(begin, ending, what, _expression, flags); begin =what[0].second; if (found) { cout<<matchescounter<<"----------"<<what[0]<<"-------------------"<<what[0].second-beginning_saved<<"\n"; matchescounter++; } } catch (std::exception &e) { cout<<*begin; of<<*begin; begin+=1; } } cout<<"---------------the end------------\n"; cout<<matchescounter; of.close(); } //--------------------------------------------------------------------------------------- I have noticed that the problem happens not with all large files, but with quite a bit of them. After I have received the problematic section in my file, I ran the program on it and it did not raise any exceptions. Please , help me I have a Graduate project to complete within 3 weeks from now, and this is one of the major bugs I have not resolved. Yours truely, Kosta. Desparatly waiting for your reply. --------------------------------- Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. [View Less]

2 1

RE: [Boost-users] polymorphic container/boost::any
by Klaus Nowikow 13 Aug '04

13 Aug '04

> dp12-ipvi(a)spamex.com wrote: > > Use std::list<boost::shared_ptr> std::list<boost::shared_ptr<tree> > to be exact ;-) > > I hope I spelled all that correctly. > > ++PLS -- Klaus > > -----Original Message----- > From: goochrules! [mailto:goochrules@gmail.com] > Sent: Thursday, August 12, 2004 2:02 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] polymorphic container/boost::any > > * Replies will be … [View More]sent through Spamex to boost-users(a)lists.boost.org > * For additional info click -> http://www.spamex.com/i/?v=4259897 > I'm quite sure that this problem has been addressed many > times before, so I > suspect it as a better name and I suspect that boost::any could be the > solution. > I want to store related types in the same stl container, for > instance, this > is the class heirachy I want: > class tree { public: void grow() =0; }; > class oak : public tree { public: void grow() { std::cout << > "oak grows > slowly" << std::endl; }; class pine : public tree { public: > void grow() { > std::cout << "pine grows quickly" << std::endl; }; Then, I > try to put them > in a std::list: > std::list< tree > forest; > forest.push_back(oak()); > forest.push_back(pine()); > ...and I find out that I can't define tree::grow as abstract. > So I give it > a dummy implentation -- void grow() { std::cout << "tree grows" << > std::endl; --, and try to iterate over the objects: > for(std::list< tree >::iterator iter = forest.begin(); > forest.end() != iter; > ++iter) { > iter->grow(); > } > ...and I don't get what I expect: > tree grows > tree grows > I then think about trying to use a std::list< tree& > and > discover that it > won't compile. I think briefly consider std::list< tree* > > but decide this > dosen't meet requirements of memory management. > So I do some searching for 'polymorphic container' and 'polymorphic > iterator' and come up with boost::any, but I've no luck in > making it work. > Attached is my code. > In the end, I'm looking for a way to add related types to a > stl container > and not have to do anything complicated to call a method on the type's > abstract interface and to not have to wory about memory > management. Maybe > this question is better suited for comp.lang.c++[.moderated]? > -- Matthew Peltzer > -- goochrules(a)gmail.com > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > [View Less]

1 0

compiling boost using Intel C++ 8.0 under Windows
by Lars Schouw 13 Aug '04

13 Aug '04

I am havng problems building boost using the intel C++ 8.0 compiler. It looks as if bjam can't fine the icl.exe compiler executable itself. This file is installed under this directory C:\Program Files\Intel\CPP\Compiler80\Ia32\Bin Any ideas what I do wrong? I try this: run the iclvars.bat batch file. Then I use bjam like this: C:\dev\boost\boost_1_31_0_icc>bjam "-sTOOLS=intel-win32" "-sINTEL_VERSION=80" "-sINTEL_BASE_MSVC_TOOLSET=vc7.1" But when compiling I get these errors from each … [View More]

1 0

RE: [Boost-users] polymorphic container/boost::any
by dp12-ipvi＠spamex.com 12 Aug '04

12 Aug '04

Use std::list<boost::shared_ptr> I hope I spelled all that correctly. ++PLS -----Original Message----- From: goochrules! [mailto:goochrules@gmail.com] Sent: Thursday, August 12, 2004 2:02 PM To: boost-users(a)lists.boost.org Subject: [Boost-users] polymorphic container/boost::any * Replies will be sent through Spamex to boost-users(a)lists.boost.org * For additional info click -> http://www.spamex.com/i/?v=4259897 I'm quite sure that this problem has been addressed many times … [View More]

1 0

Random Library
by Andy Tompkins 12 Aug '04

12 Aug '04

Hi, I have a question about the random library. I'm using vc7.1 and I'm getting a warning when I include the random library. The warning I get when I, #include <boost\random.hpp> is: d:\includes\boost_1_31_0\boost\random\linear_congruential.hpp(233) : warning C4244: 'return' : conversion from 'boost::uint64_t' to 'boost::int32_t', possible loss of data When I look at the file, rand48::operator() returns an int32_t, but lcf is defined with uint64_t. Thanks in advance for any help. Andy.

1 0