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

BOOST_STATIC_CONST
by Michael Held 01 Dec '06

01 Dec '06

hi, I am using BOOST_STATIC_CONST for static class members of a base class. I have following situation: template <int T> class A { typedef typename MyType<T>::value_type value_type; BOOST_STATIC_CONST(typename value_type::some_type, MY_CONSTANT = 0); }; template <int T> class B : public A<T> { typedef A<T> Base; typedef typename Base::value_type value_type; BOOST_STATIC_CONST(typename value_type::some_type, MY_CONSTANT = Base::MY_CONSTANT); }; or template <int T> class B : public A<T> { typedef A<T> Base; typedef typename Base::value_type value_type; using Base::MY_CONSTANT; }; for both cases I got a linker error: /usr/bin/ld: Undefined symbols: B<0>::MY_CONSTANT what am I doing wrong? I am using darwin gcc4.0.1 and Boost from CVS thanks a lot! michael

2 1

Re: [Boost-users] [Serialization] Linker Errors Using Unicode(Was:error C2027: useofundefinedtype'boost::serialization::extended_type_info_null<T>'?)
by Lawrence Spector 30 Nov '06

30 Nov '06

Ok, I was playing with the compiler settings and figured it out. Apparently, in order to use this, you *must* have wchar_t treated as a built-in type setting on in VC7.1. Ah ha. Maybe there's a good spot to document that. Thanks for the assistance, Lawrence

2 1

Re: [Boost-users] Suggestion for boost`s smart pointers
by Sohail Somani 30 Nov '06

30 Nov '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Ilya Sokolov > sorry for such late response, i think you should also consider > Andrei and Petru's ScopeGuard from > http://www.ddj.com/dept/cpp/184403758 I think such an idea mixed with tr1/boost bind would be very useful. Though I'm just looking for a way to deallocate stuff allocated by a C library.

1 0

Re: [Boost-users] [Serialization] Linker Errors Using Unicode(Was:error C2027: useofundefinedtype'boost::serialization::extended_type_info_null<T>'?)
by Lawrence Spector 30 Nov '06

30 Nov '06

Ok. Well, I tried testarray.cpp (which contains the test_array_text_warchive test) and it doesn't build in VC7.1, with the following linker errors, if I turn on the unicode option. I simply made a new project and turned on unicode, and added the file. I don't see why that should have any issues. I have yet to try with 1.34, but I can't see a logical reason why unicode doesn't work, but non-unicode does. I'll get back with the result of 1.34, but again, 1.33.1 does not link for me. The results are as follows: ------ Build started: Project: test_array_text_archive, Configuration: Debug Win32 ------ Linking... Creating library Debug/test_array_text_archive.lib and object Debug/test_array_text_archive.exp testarray.obj : error LNK2019: unresolved external symbol "void __cdecl boost::test_tools::tt_detail::check_impl(class boost::test_tools::predicate_result const &,class boost::basic_wrap_stringstream<char> &,class boost::unit_test::basic_cstring<char const >,unsigned int,enum boost::test_tools::tt_detail::tool_level,enum boost::test_tools::tt_detail::check_type,unsigned int,...)" (?check_impl@tt_detail@test_tools@boost@@YAXABVpredicate_result@23@AAV?$ basic_wrap_stringstream@D@3@V?$basic_cstring@$$CBD@unit_test@3@IW4tool_l evel@123@W4check_type@123@IZZ) referenced in function "int __cdecl test_array<class A>(class A)" (??$test_array@VA@@@@YAHVA@@@Z) testarray.obj : error LNK2019: unresolved external symbol "public: void __thiscall boost::archive::text_oarchive_impl<class boost::archive::text_oarchive>::save(class std::basic_string<unsigned short,struct std::char_traits<unsigned short>,class std::allocator<unsigned short> > const &)" (?save@?$text_oarchive_impl@Vtext_oarchive@archive@boost@@@archive@boost @@QAEXABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@@Z ) referenced in function "public: static void __cdecl boost::archive::save_access::save_primitive<class boost::archive::text_oarchive,class std::basic_string<unsigned short,struct std::char_traits<unsigned short>,class std::allocator<unsigned short> > >(class boost::archive::text_oarchive &,class std::basic_string<unsigned short,struct std::char_traits<unsigned short>,class std::allocator<unsigned short> > const &)" (??$save_primitive@Vtext_oarchive@archive@boost@@V?$basic_string@GU?$cha r_traits@G@std@@V?$allocator@G@2@@std@@@save_access@archive@boost@@SAXAA Vtext_oarchive@12@ABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@ G@2@@std@@@Z) testarray.obj : error LNK2019: unresolved external symbol "public: void __thiscall boost::archive::text_iarchive_impl<class boost::archive::text_iarchive>::load(class std::basic_string<unsigned short,struct std::char_traits<unsigned short>,class std::allocator<unsigned short> > &)" (?load@?$text_iarchive_impl@Vtext_iarchive@archive@boost@@@archive@boost @@QAEXAAV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@@Z ) referenced in function "public: static void __cdecl boost::archive::load_access::load_primitive<class boost::archive::text_iarchive,class std::basic_string<unsigned short,struct std::char_traits<unsigned short>,class std::allocator<unsigned short> > >(class boost::archive::text_iarchive &,class std::basic_string<unsigned short,struct std::char_traits<unsigned short>,class std::allocator<unsigned short> > &)" (??$load_primitive@Vtext_iarchive@archive@boost@@V?$basic_string@GU?$cha r_traits@G@std@@V?$allocator@G@2@@std@@@load_access@archive@boost@@SAXAA Vtext_iarchive@12@AAV?$basic_string@GU?$char_traits@G@std@@V?$allocator@ G@2@@std@@@Z) LIBCD.lib(crt0.obj) : error LNK2019: unresolved external symbol _main referenced in function _mainCRTStartup Debug/test_array_text_archive.exe : fatal error LNK1120: 4 unresolved externals Build log was saved at "file://c:\Work\Sandbox\Boost\Serialization\test_array_text_archive\Debu g\BuildLog.htm" test_array_text_archive - 5 error(s), 0 warning(s) ---------------------- Done ---------------------- Build: 0 succeeded, 1 failed, 0 skipped -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Robert Ramey Sent: Thursday, November 30, 2006 2:14 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] [Serialization] Linker Errors Using Unicode(Was:error C2027: useofundefinedtype'boost::serialization::extended_type_info_null<T>'?) Note that all tests (all 50 of them) work with all archive classes that the platform supports. It has been this way since the beginning. As far as I know there is nothing to fix. Robert Ramey Lawrence Spector wrote: > Okay, that's fair and fine. However, any explanation for the linker > errors that seem to occur only with unicode versions? > > Can anyone else try out the demo.cpp example > (http://www.boost.org/libs/serialization/example/demo.cpp) with a > unicode build, and just change the boost::archive::text_oarchive and > boost::archive::text_iarchive to use boost::archive::text_woarchive > and boost::archive::text_wiarchive, as well as using wide strings and > wide streams? I want to see if anyone else has this issue with > 1.33.1? > > Any chance this might be fixed in 1.34.0? > > Thanks, > > Lawrence > > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Robert Ramey > Sent: Thursday, November 30, 2006 11:47 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [Serialization] error C2027: use of > undefinedtype'boost::serialization::extended_type_info_null<T>'? > > Note that the library is in two parts. libboost_serialization.. > contains > code used for all types of archives while libboost_wserialization > contains > code used only for wide character archives. So applications using > wide character archives should link against BOTH libraries. > > Robert Ramey > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] [Serialization] Linker Errors Using Unicode (Was: error C2027: use of undefinedtype'boost::serialization::extended_type_info_null<T>'?)
by Lawrence Spector 30 Nov '06

30 Nov '06

Okay, that's fair and fine. However, any explanation for the linker errors that seem to occur only with unicode versions? Can anyone else try out the demo.cpp example (http://www.boost.org/libs/serialization/example/demo.cpp) with a unicode build, and just change the boost::archive::text_oarchive and boost::archive::text_iarchive to use boost::archive::text_woarchive and boost::archive::text_wiarchive, as well as using wide strings and wide streams? I want to see if anyone else has this issue with 1.33.1? Any chance this might be fixed in 1.34.0? Thanks, Lawrence -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Robert Ramey Sent: Thursday, November 30, 2006 11:47 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] [Serialization] error C2027: use of undefinedtype'boost::serialization::extended_type_info_null<T>'? Note that the library is in two parts. libboost_serialization.. contains code used for all types of archives while libboost_wserialization contains code used only for wide character archives. So applications using wide character archives should link against BOTH libraries. Robert Ramey _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

dijkstra_shortest_paths and Python
by Hugo Ferreira 30 Nov '06

30 Nov '06

HI there, I'm trying to use the BGL bindings for python found here: http://www.osl.iu.edu/~dgregor/bgl-python/ The problem is that I can't seem to understand how the dijkstra_shortest_paths() and the corresponding graph works. My code, so far, is like this: ---8<---8<--- import boost as bgl graph = bgl.Graph() a = graph.add_vertex() b = graph.add_vertex() e = graph.add_edge(a, b) weights = graph.edge_property_map('integer') weights[e] = 5 graph.edge_properties['weight'] = weights boost.dijkstra_shortest_paths(graph, a) ---8<---8<--- Which, of course, complains about the dijkstra_shortest_paths function signature. Can anyone please provide me an working example of setting up a graph and calling this function? I basically need the shortest path from vertex A to vertex B. Thanks in advance, Hugo Ferreira -- GPG Fingerprint: B0D7 1249 447D F5BB 22C5 5B9B 078C 2615 504B 7B85

2 2

BGL: Retrieving a vertex_descriptor from a custom property?
by Peter Palotas 30 Nov '06

30 Nov '06

I'm wondering if it is somehow possible to attach a custom property (eg. a pointer to some object) to each vertex in a graph, and then lookup the vertex based on that index? My first attempt was to use a simple map outside of the graph, mapping my custom property to a vertex_descriptor, but since the vertex_descriptors seem to change as vertices are inserted and removed this does not work. Is it possible to do this using BGL? An example would be greatly appreciated. Sincerely, Peter

2 4

more lambda issues
by Noah Roberts 30 Nov '06

30 Nov '06

I'm kind of loosing faith that this list ever responds to questions but here goes anyway. I've narrowed a problem down to this: #include <iostream> #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> struct test_b { test_b() { std::cerr << "test_b::test_b()\n"; } test_b(test_b const&) { std::cerr << "test_b::test_b(test_b const&)\n"; } virtual int f() = 0; //{ return 5; } }; struct test_d : test_b { test_d() : test_b() { std::cerr << "test_d::test_d()\n"; } test_d(test_d const& d) : test_b(d) { std::cerr << "test_d::test_d(test_d const&)\n"; } int f() { return 5; } }; int main(void) { namespace l = boost::lambda; test_b & td = test_d(); std::cerr << "Value: " << (l::bind(&test_b::f, l::_1))(td) << "\n"; int x; std::cin >> x; } Compiler result: cannot instantiate abstract class test_b. Because lambda doesn't seem to be able to handle smart pointers at all I have been trying to come up with a way to pass the dereferenced result into the function call. Nothing is working. In the end lambda must be able to handle the above in order to make this work. If lambda cannot handle this simple case I just don't see how it can be any use. The full compiler output follows: 1>c:\boost\include\boost-1_33_1\boost\tuple\detail\tuple_basic.hpp(419) : error C2259: 'test_b' : cannot instantiate abstract class 1> due to following members: 1> 'int test_b::f(void)' : is abstract 1> c:\documents and settings\nroberts\my documents\visual studio 2005\projects\playground\playground\playground.cpp(14) : see declaration of 'test_b::f' 1> c:\boost\include\boost-1_33_1\boost\tuple\detail\tuple_basic.hpp(329) : see reference to class template instantiation 'boost::tuples::cons<HT,TT>' being compiled 1> with 1> [ 1> HT=test_b, 1> TT=boost::lambda::detail::deduce_non_ref_argument_types_<boost::tuples::cons<const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>,boost::tuples::detail::map_tuple_to_cons<boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>::type>::tail_type,boost::tuples::tuple<test_b &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type 1> ] 1> c:\boost\include\boost-1_33_1\boost\lambda\detail\lambda_functor_base.hpp(151) : see reference to class template instantiation 'boost::tuples::cons<HT,TT>' being compiled 1> with 1> [ 1> HT=int (__thiscall test_b::* const )(void), 1> TT=boost::tuples::cons<test_b,boost::lambda::detail::deduce_non_ref_argument_types_<boost::tuples::cons<const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>,boost::tuples::detail::map_tuple_to_cons<boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>::type>::tail_type,boost::tuples::tuple<test_b &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type> 1> ] 1> c:\boost\include\boost-1_33_1\boost\lambda\detail\lambda_functor_base.hpp(228) : see reference to class template instantiation 'boost::lambda::detail::has_null_type<Tuple>' being compiled 1> with 1> [ 1> Tuple=boost::tuples::cons<int (__thiscall test_b::* const )(void),boost::tuples::cons<test_b,boost::lambda::detail::deduce_non_ref_argument_types_<boost::tuples::cons<const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>,boost::tuples::detail::map_tuple_to_cons<boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>::type>::tail_type,boost::tuples::tuple<test_b &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type>>::type>> 1> ] 1> c:\boost\include\boost-1_33_1\boost\lambda\detail\lambda_functor_base.hpp(398) : see reference to class template instantiation 'boost::lambda::detail::deduce_non_ref_argument_types<Args,SigArgs>' being compiled 1> with 1> [ 1> Args=boost::tuples::tuple<int (__thiscall test_b::* const )(void),const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>, 1> SigArgs=boost::tuples::tuple<test_b &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type> 1> ] 1> c:\documents and settings\nroberts\my documents\visual studio 2005\projects\playground\playground\playground.cpp(32) : see reference to class template instantiation 'boost::lambda::lambda_functor_base<Act,Args>::sig<SigArgs>' being compiled 1> with 1> [ 1> Act=boost::lambda::action<2,boost::lambda::function_action<2>>, 1> Args=boost::tuples::tuple<int (__thiscall test_b::* const )(void),const boost::lambda::lambda_functor<boost::lambda::placeholder<1>>,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type,boost::lambda::detail::bind_traits<boost::tuples::null_type>::type>, 1> SigArgs=boost::tuples::tuple<test_b &,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type,boost::tuples::null_type> 1> ]

5 7

Re: [Boost-users] Suggestion for boost`s smart pointers
by Sohail Somani 30 Nov '06

30 Nov '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of mark cox > Sent: Tuesday, November 28, 2006 2:37 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Suggestion for boost`s smart pointers > > wow, this seems like a great idea, a scoped_ptr with deleter > would be v.useful. > mark I've been thinking something like (just something I hacked together just now). Not sure if there is a nicer way. #include <string> #include <cstdio> #include <iostream> template<typename T> struct DeletingDeleter { DeletingDeleter(T * p) { delete p; std::cout << "DeletingDeleter" << std::endl; } }; struct FileCloser { FileCloser(FILE * f) { std::cout << "Closing file" << std::endl; fclose(f); } }; template<typename T, typename Deleter=DeletingDeleter<T> > struct scoped_ptr { scoped_ptr():p_(0){} scoped_ptr(T * p):p_(p){} ~scoped_ptr() { Deleter d(p_); } T * get() {return p_;} // regular stuff private: T * p_; }; typedef scoped_ptr<FILE,FileCloser> file_ptr; int main() { scoped_ptr<int> a; // maintain old interface scoped_ptr<int> b(new int(5)); file_ptr p(fopen("myfile.txt","w")); fprintf(p.get(),"Hello world!\n"); }

5 5

Re: [Boost-users] [Serialization] error C2027: use of undefined type 'boost::serialization::extended_type_info_null<T>'?
by Lawrence Spector 30 Nov '06

30 Nov '06

Ok, I got past the errors I was having last night. Seemed to have to do with the ordering of the libraries and then an incorrect constant used in the load method. Moving on, I now get the following linker errors: Linking... Creating library Debug/SerializationDemo.lib and object Debug/SerializationDemo.exp demo.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::archive::basic_text_oprimitive<class std::basic_ostream<unsigned short,struct std::char_traits<unsigned short> > >::~basic_text_oprimitive<class std::basic_ostream<unsigned short,struct std::char_traits<unsigned short> > >(void)" (??1?$basic_text_oprimitive@V?$basic_ostream@GU?$char_traits@G@std@@@std @@@archive@boost@@QAE@XZ) referenced in function "public: __thiscall boost::archive::text_woarchive_impl<class boost::archive::text_woarchive>::~text_woarchive_impl<class boost::archive::text_woarchive>(void)" (??1?$text_woarchive_impl@Vtext_woarchive@archive@boost@@@archive@boost@ @QAE@XZ) demo.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::archive::text_wiarchive_impl<class boost::archive::text_wiarchive>::text_wiarchive_impl<class boost::archive::text_wiarchive>(class std::basic_istream<unsigned short,struct std::char_traits<unsigned short> > &,unsigned int)" (??0?$text_wiarchive_impl@Vtext_wiarchive@archive@boost@@@archive@boost@ @QAE@AAV?$basic_istream@GU?$char_traits@G@std@@@std@@I@Z) referenced in function "public: __thiscall boost::archive::text_wiarchive::text_wiarchive(class std::basic_istream<unsigned short,struct std::char_traits<unsigned short> > &,unsigned int)" (??0text_wiarchive@archive@boost@@QAE@AAV?$basic_istream@GU?$char_traits @G@std@@@std@@I@Z) demo.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::archive::basic_text_iprimitive<class std::basic_istream<unsigned short,struct std::char_traits<unsigned short> > >::~basic_text_iprimitive<class std::basic_istream<unsigned short,struct std::char_traits<unsigned short> > >(void)" (??1?$basic_text_iprimitive@V?$basic_istream@GU?$char_traits@G@std@@@std @@@archive@boost@@QAE@XZ) referenced in function "public: __thiscall boost::archive::text_wiarchive_impl<class boost::archive::text_wiarchive>::~text_wiarchive_impl<class boost::archive::text_wiarchive>(void)" (??1?$text_wiarchive_impl@Vtext_wiarchive@archive@boost@@@archive@boost@ @QAE@XZ) demo.obj : error LNK2019: unresolved external symbol "public: __thiscall boost::archive::basic_text_oprimitive<class std::basic_ostream<unsigned short,struct std::char_traits<unsigned short> > >::basic_text_oprimitive<class std::basic_ostream<unsigned short,struct std::char_traits<unsigned short> > >(class std::basic_ostream<unsigned short,struct std::char_traits<unsigned short> > &,bool)" (??0?$basic_text_oprimitive@V?$basic_ostream@GU?$char_traits@G@std@@@std @@@archive@boost@@QAE@AAV?$basic_ostream@GU?$char_traits@G@std@@@std@@_N @Z) referenced in function "public: __thiscall boost::archive::text_woarchive_impl<class boost::archive::text_woarchive>::text_woarchive_impl<class boost::archive::text_woarchive>(class std::basic_ostream<unsigned short,struct std::char_traits<unsigned short> > &,unsigned int)" (??0?$text_woarchive_impl@Vtext_woarchive@archive@boost@@@archive@boost@ @QAE@AAV?$basic_ostream@GU?$char_traits@G@std@@@std@@I@Z) Debug/SerializationDemo.exe : fatal error LNK1120: 4 unresolved externals However, if I change the build type to not be unicode, then it all compiles, links, and works. I checked to see what libraries are being linked in a non- unicode build vs. a unicode: Non-Unicode: Linking to lib file: libboost_serialization-vc71-sgd-1_33_1.lib // Good Linking to lib file: libboost_serialization-vc71-sgd-1_33_1.lib // Good Unicode: Linking to lib file: libboost_wserialization-vc71-sgd-1_33_1.lib // Good Linking to lib file: libboost_serialization-vc71-sgd-1_33_1.lib // Why?? Linking to lib file: libboost_serialization-vc71-sgd-1_33_1.lib // Why?? Any ideas? Does the boost serialization possibly have unicode issues in 1.33.1? Thanks in advance, Lawrence

2 1