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

RE: [Boost-Users] Boost::Filesystem: Directory iterator and dangling links
by Ben Hutchings 23 Apr '03

23 Apr '03

You wrote: <snip> > In the case of dangling links I obtain a not_found_error. > This seems to be a contradiction. First I find something (and obtain an > iterator) and without any interference from > outside is_directory() tells me it cannot find the object. > The problem is that directory_iterator refers to the link whereas > is_directory() and the following exception refer to the target (which is > missing). <snip> To make this consistent, then, maybe is_directory() and friends should be using lstat rather than stat on Unix. Is it desirable that links be resolved? I suppose it is if the iterator is being used to walk a whole tree - but not if it's being used to list a single directory. Perhaps there is a need to include explicit support for links in the API. Windows has supported them since 2000, so they aren't just a Unix thing now.

2 1

RE: [Boost-Users] simplest pool_alloc example does not work on VC 6
by Beman Dawes 22 Apr '03

22 Apr '03

At 01:40 PM 4/22/2003, scleary(a)jerviswebb.com wrote: >> -----Original Message----- >> From: Ben Hutchings [mailto:ben.hutchings@businesswebsoftware.com] >>... >> The VC++ 7 compiler is good enough to support standard allocators and >> the library does use them. With the addition of a variable name and >> semi-colon, the given example can be compiled with this version. > >Glad to hear it. Too bad it's not released yet. Ben is probably talking about 7.0, which has been released for a year or so. VC++ 7.1 will be released officially Thursday, the 24th, IIRC. Using the VC++ 7.1 final beta, test_pool_alloc is passing OK. --Beman

1 0

RE: [Boost-Users] simplest pool_alloc example does not work on VC6
by Ben Hutchings 22 Apr '03

22 Apr '03

scleary(a)jerviswebb.com wrote: > Ben Hutchings <ben.hutchings(a)businesswebsoftware.com> wrote: > > scleary(a)jerviswebb.com wrote: > > > Sorry, Boost.Pool does not currently support MSVC, due to that compiler's > > > extreme lack of template support. <snip> > > The VC++ 7 compiler is good enough to support standard allocators and > > the library does use them. With the addition of a variable name and > > semi-colon, the given example can be compiled with this version. > > Glad to hear it. Too bad it's not released yet. Where have you been for the last year?

1 0

Newbie boost help needed..
by Bryan Coon 22 Apr '03

22 Apr '03

Hi, I am totally new to boost and just wanted to ask a couple of simple questions... First, I compiled the boost libraries okay with msvc. I updated the include path in my vc++ 6.0, and can include boost files via #include <boost/xxx.hpp>. So far so good! I wanted to try some things out, like boost's mersenne twister random number generator. I first did this: #include <boost/random/mersenn_twister.hpp> And got no errors. Then I read there was a random.hpp for convenience so I changed this to: #include <boost/random.hpp> And received as a reward complaints: d:\dev\devproject\boost_1_30_0\boost\random\uniform_01.hpp(44) : error C2275: 'std::numeric_limits<`template-parameter258'>::is_integer' : illegal use of this type as an expression d:\dev\devproject\boost_1_30_0\boost\random\uniform_01.hpp(95) : see reference to class template instantiation 'boost::uniform_01<UniformRandomNumberGenerator,RealType>' being compiled There were 6 of these errors. What am I doing wrong? Also, is there a way to include the boost libs in vc++ where I get the autocompletion if I use boost:: ? It is very difficult to figure out how the libs are supposed to be used (for me) by looking at example code or the documentation. Autocompletion as if boost were part of my project would be very useful. Thanks, B

1 0

RE: [Boost-Users] simplest pool_alloc example does not work on VC6
by Ben Hutchings 22 Apr '03

22 Apr '03

scleary(a)jerviswebb.com wrote: > Sorry, Boost.Pool does not currently support MSVC, due to that compiler's > extreme lack of template support. <snip> For VC++ 6, all that should be needed is a _Charalloc function (instead of struct rebind) and a change to the type of deallocate's first parameter (to void *, which actually makes more sense). The VC++ 7 compiler is good enough to support standard allocators and the library does use them. With the addition of a variable name and semi-colon, the given example can be compiled with this version. Is there some other reason why VC++ cannot be supported?

1 0

simplest pool_alloc example does not work on VC6
by John Harris 22 Apr '03

22 Apr '03

Using Boost 1.30.0. MSVC6 Tow problems: (1) I have to #define __WIN32__, and (2) Doesn't compile Am I doing something wrong, here? #include "afxwin.h" #include <map> #define __WIN32__ // why do I have to define this??? #include "boost/pool/pool_alloc.hpp" int main() { std::map<int,int,std::less<int>, boost::pool_allocator<int> > return 0; } :\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xtree(587) : error C2664: 'deallocate' : cannot convert parameter 1 from 'struct std::_Tree<int,struct std::pair<int const ,int>,struct std::map<int,int,struct std::less<int>,class boost::pool_al locator<int,struct boost::default_user_allocator_new_delete,class boost::details::pool::win32_mutex,32> >::_Kfn,struct std::less<int>,class boost::pool_allocator<int,struct boost::default_user_allocator_new_delete,class boost::details::pool::win32_m utex,32> >::_Node *' to 'int *const ' Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xtree (587) : while compiling class-template member function 'void __thiscall std::_Tree<int,struct std::pair<int const ,int>,struct std::map<int,int,struct std::less<int>,class boost::poo l_allocator<int,struct boost::default_user_allocator_new_delete,class boost::details::pool::win32_mutex,32> >::_Kfn,struct std::less<int>,class boost::pool_allocator<int,struct boost::default_user_allocator_new_delete,class boost::details::pool::win 32_mutex,32> >::_Freenode(struct std::_Tree<int,struct std::pair<int const ,int>,struct std::map<int,int,struct std::less<int>,class boost::pool_allocator<int,struct boost::default_user_allocator_new_delete,class boost::details::pool::win32_mutex,32 > >::_Kfn,struct std::less<int>,class boost::pool_allocator<int,struct boost::default_user_allocator_new_delete,class boost::details::pool::win32_mutex,32> >::_Node *)'

1 0

boost::thread warnings?
by olexander_shyrokov 21 Apr '03

21 Apr '03

I got some warnings when compiling my program (see below). I am using Visual Studio C++ 6 and STLport 4.5.3 I've seen some questions about this issue in the mailing list, but did not get the feeling that I understand what is going on and when I can safly ignore them? Thanks a lot. c:\src\boost\boost\thread\exceptions.hpp(29) : warning C4275: non dll-interface class '_STL::logic_error' used as base for dll-interface class 'boost::lock_error' c:\progra~1\micros~3\vc98\include\stlport\stdexcept(72) : see declaration of 'logic_error' c:\src\boost\boost\thread\exceptions.hpp(35) : warning C4275: non dll-interface class '_STL::runtime_error' used as base for dll-interface class 'boost::thread_resource_error' c:\progra~1\micros~3\vc98\include\stlport\stdexcept(80) : see declaration of 'runtime_error' c:\src\boost\boost\thread\mutex.hpp(37) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::mutex' c:\src\boost\boost\noncopyable.hpp(22) : see declaration of 'noncopyable' c:\src\boost\boost\thread\mutex.hpp(75) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::try_mutex' c:\src\boost\boost\noncopyable.hpp(22) : see declaration of 'noncopyable' c:\src\boost\boost\thread\mutex.hpp(115) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::timed_mutex' c:\src\boost\boost\noncopyable.hpp(22) : see declaration of 'noncopyable' c:\src\boost\boost\thread\thread.hpp(39) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::thread' c:\src\boost\boost\noncopyable.hpp(22) : see declaration of 'noncopyable' c:\src\boost\boost\thread\thread.hpp(68) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::thread_group' c:\src\boost\boost\noncopyable.hpp(22) : see declaration of 'noncopyable' c:\src\boost\boost\thread\thread.hpp(79) : warning C4251: 'm_threads' : class '_STL::list<class boost::thread *,class _STL::allocator<class boost::thread *> >' needs to have dll-interface to be used by clients of class 'boost::thread_group'

1 0

Problems linking with Boost 1.29.0 thread lib, Linux/g++ 3.2.2 -r2
by subsample 21 Apr '03

21 Apr '03

Failing to link a program with libboost_thread, even though I supply the -lboost_thread directive in the makefile. I'm kind of new to makefiles, having only used Visual C++ in Windows untill recently. I 've tried changing things around a bit, doesn't help. A minimal test program I wrote links fine with boost_thread though. My makefile looks like this: CC=g++ CFLAGS=-g LDFLAGS=-L/home/sub/Libs/alsa/lib -lasound -lboost_thread -lpthread alsatest: alsatest.o $(CC) $(LDFLAGS) -o alsatest SmallObj.o alsatest.o alsatest.o: smallobj.o $(CC) $(CFLAGS) alsatest.cpp -c smallobj.o: $(CC) $(CFLAGS) /usr/include/loki/SmallObj.cpp -c clean: rm -f *.o alsatest g++ complains about the same missing references no matter if I include the -lboost_thread or not. If someone could point out what I'm doing wrong I'd be grateful : )

1 1

Typo in boost/config/compiler/visualc.hpp
by Vaclav Vesely 19 Apr '03

19 Apr '03

line 26: #if (_MSC_VER <= 1300) // 1200 == VC++ 7.0 The comment is inconsistent with the code. Regards, w

2 1

RE: [Boost-Users] lexical_cast regression
by Tom Matelich 18 Apr '03

18 Apr '03

> From: Terje Slettebø [mailto:tslettebo@chello.no] > > >From: "Tom Matelich" <tmatelich(a)zetec.com> > > > I haven't gone and looked at the boost ml archives to track > > the reason for > > this down, but the addition of stream.unsetf(std::ios::skipws) in > > lexical_cast caused some of our code to fail. I've commented it out > > locally, and was wondering why it was decided this is more > > appropriate default behavior. > > It was done to avoid the problems with throwing exceptions on > whitespace. > For example, without it, the following would throw a bad_lexical_cast: > > lexical_cast<std::string>(' '); // A space character > > What kind of code is the current version failing at? > We have some legacy files that are converted to xml through some process (I didn't write it) and it ends up with space-padded strings for ints. So the test case was dying converting " 86" to an int. I can see its purpose, except that example wouldn't happen because of the std::string overload, right? Tom ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

2 1