- Boost - lists.boost.org

pqs - physical quantities library
by Andy Little 10 Nov '04

10 Nov '04

Hi, I have been continuing with my physical-quantities library over the last year, http://www.servocomm.freeserve.co.uk/Cpp/physical_quantity/index.html and I am now seeking feedback as to whether it is worth putting this forward as a boost library proposal.... *Overview* The physical-quantity type-family provides methods for modeling physical-quantities in C++ programs. The advantages and extra functionality over inbuilt types used in the role include, compile time dimensional-analysis checking, automatic conversion between units and an increase in source code comprehensibility. The type family includes two types, firstly a type where the units are fixed at compile-time referred to in the text as a ct-quantity and secondly a type where the units can be run-time modified, referred to in the text as an rt-quantity. The ct-quantity has many similar features to an inbuilt-type: - concrete type with simple,consistent semantics close to those of inbuilt-types. - aims for speed and code size performance close to that of in-built types. - requires no special framework to use. *Application areas* The application areas are very wide, including scientific-engineering, CAD, 3D games programming among many others. *Future directions* 2D and 3D vector quantities, scene-graphs and scene-modelling, Graphics interface (eg OpenGL), splines and curve analysis, successive approaximation , piecewise differentiation and integration algorithms. finite element analysis, etc etc. Issues from the previous thread on the library and physical quantities in general http://aspn.activestate.com/ASPN/Mail/Message/boost/1926782 issue: Angles. current status: Angles are implemented.There are two types, irrational (ie radians) and rational fractions of revolution ie degrees minutes etc). radians are what you might call a 'weak type'. (Though this behaviour can be modified by a macro switch). They will implicitly decay to (say) double and can be implicitly cast to double. However they also allow implicit conversions to and from degrees etc. hence an implicit conversion from degrees to radians can occur if a function has a radians argument, but not a double argument. They are also useful for output of units. --------------------- issue: Differentiating different but dimensionally equivalent types. current status: This is implemented. --------------------- issue: Implicit conversions between units. current status: Implicit conversions are intrinsic. They are practical instinctive and useful. --------------------- issue: You should be using mpl. current status: Hopefully I will be able to get hold of the metaprogramming book soon, at which point I can decide whether there are advantages. --------------------- regards Andy Little

4 10

Re: Problem to use boost
by Daniel Lidström 10 Nov '04

10 Nov '04

> "Daniel Lidström" <daniel.lidstrom(a)sbg.se> wrote in message > news:E1F34343C3A0804BB3E29ABBFCBBAF0C01BB6F@ADA... > > Hi, > > > > this is what I've done: > > compiled with commandline of > > bjam "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET > > 2003\Vc7" > > "--prefix=C:\projects\boost" install > > I don't see an -sTOOLS=vc7.1 here telling bjam which tool set > to use, as the > Getting Started page suggests. I'd guess this is confusing > things. Given you > are using the default root for vc7.1 try: > > bjam -sTOOLS=vc7.1 "--prefix=C:\projects\boost" install > > note that vc7.1 is case sensitive. > Ok, I compile like this: bjam "-sTOOLS=vc7.1" "--prefix=C:\projects\boost" install > > Within my project, I've set an additional include path of > > C:\projects\boost\include\boost-1_31. Now when I compile my > project with > > > > one source file containing the line > > > > #include <boost/shared_ptr.hpp> > > > > I get this error: > > > > > c:\projects\boost\include\boost-1_31\boost\config\compiler\bor > land.hpp(1 > > 3) > > : fatal error C1017: invalid integer constant expression > > > > What have I missed? I do the same as before and get the same error. And yes, I am using Visual Studio 7.1 in case anyone thought else. What am I doing wrong? -- Daniel

2 1

[boost][boost-users][random] Open bugs
by Cromwell Enage 10 Nov '04

10 Nov '04

Any chance that any of the following bug reports will be resolved before the release? <http://sourceforge.net/tracker/index.php?func=detail&aid=911758&group_id=75…> <http://sourceforge.net/tracker/index.php?func=detail&aid=715667&group_id=75…> <http://sourceforge.net/tracker/index.php?func=detail&aid=652567&group_id=75…> TIA! Cromwell Enage __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

2 1

[serialization] problem with Microsoft VC 7.1 and ADL
by Vyacheslav E. Andrejev 09 Nov '04

09 Nov '04

Hello All, Seriaization library relies on argument dependent lookup (ADL) in calling load and save functions in boost::serialization::free_loader::invoke and boost::serialization::free_saver::invoke accordingly. Library supposes that this feature works well in VC 7.1 (that is macro BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP is undefined). But as I see, first, this supposition is implemented with error, and, second, ADL not always works very well in VC 7.1. Let's look to file /boost/serialization/split_free.hpp: namespace serialization { #if ! BOOST_WORKAROUND(BOOST_MSVC, <= 1300) template<class Archive, class T> void save(Archive &ar, const T & t, const unsigned int); template<class Archive, class T> void load(Archive &ar, T & t, const unsigned int); #endif ... Pay attention to "!" sign before BOOST_WORKAROUND. So, if VC version is 7.1 or higher, compiler expects that save and load would be defined in serialization namespace, if VC version is 7.0 or lower, compiler will search those namespaces from which Archive or T are originated. Very well. But let's take a look now to /boost/serialization/set.hpp for example: #ifdef BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP namespace boost { namespace serialization { #else namespace STD { #endif template<class Archive, class Key, class Compare, class Allocator > inline void save( Archive & ar, const STD::set<Key, Compare, Allocator> &t, const unsigned int /* file_version */ ){ ... } template<class Archive, class Key, class Compare, class Allocator > inline void load( Archive & ar, STD::set<Key, Compare, Allocator> &t, const unsigned int /* file_version */ ){ ... } In this file if BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP is defined save and load will be defined in serialization namespace, otherwise in the std namespace. But BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP is undefined for VC 7.1 (see /boost/config/compiler/visualc.hpp)! So in VC 7.1, accordingly to split_free.hpp, compiler expects save and load from serialization workspace, but they are defind in std accordingly to set.hpp (and all others stanard containers serialization files). By happy concourse of circumstances, this error is bypassed by errors in compiler and in most casses VC 7.1 compiles serialization library very well. But sometimes it accedentally rembers what ADL is and emits error during link stage that serialization::save and serialization::load are undefined. I suggest: 1) define BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP for VC 7.1 since as I can see Koening search technique implementation is unstable; 2) change "#if ! BOOST_WORKAROUND(BOOST_MSVC, <= 1300)" in split_free.hpp to "#if defined(BOOST_NO_ARGUMENT_DEPENDENT_LOOKUP)". -- Vyacheslav E. Andrejev System Architect, Excelsior, LLC

2 1

[filesystem]1.32/vc7.1: unresolved reference when building a user dll
by Francis ANDRE 09 Nov '04

09 Nov '04

Hi Developpers When using the dll version of the boost::filesystem library to build a user's dll library, one get the followin link error: (Note that no error is produced at link time when building a static non dll user's library with the boost::filesystem dll library) SYSOUT.obj : error LNK2019: unresolved external symbol "private: void __thiscall boost::filesystem::path::iterator::increment(void)" (?increment@iterator@path@filesystem@boost@@AAEXXZ) referenced in function "public: static void __cdecl boost::iterator_core_access::increment<class boost::filesystem::path::iterator>(class boost::filesystem::path::iterator &)" (??$increment@Viterator@path@filesystem@boost@@@iterator_core_access@boost@@ SAXAAViterator@path@filesystem@1@@Z) Any idea how to solve this unresolved reference?? The code involved in this build is: class __declspec(dllexport) SYSOUT : public OSDDIR { void makedir(const DATASET::VOLUME& volume, const std::string& file); }; void SYSOUT::makedir(const VOLUME& volume, const std::string& file) { path rel(file); path vol(volume); for (path::iterator i = rel.begin(); i != rel.end(); i++) { path dir = vol / *i; if (!boost::filesystem::exists(dir)) { create_directory(dir); } vol = vol / *i; } } Regards Francis ANDRE

2 1

Problem to use boost
by Daniel Lidström 09 Nov '04

09 Nov '04

Hi, this is what I've done: compiled with commandline of bjam "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7" "--prefix=C:\projects\boost" install Within my project, I've set an additional include path of C:\projects\boost\include\boost-1_31. Now when I compile my project with one source file containing the line #include <boost/shared_ptr.hpp> I get this error: c:\projects\boost\include\boost-1_31\boost\config\compiler\borland.hpp(1 3) : fatal error C1017: invalid integer constant expression What have I missed? -- Daniel

2 1

RE: [boost] Problem to use boost
by Michiel Salters 09 Nov '04

09 Nov '04

Are you really compiling with VC7.1, perhaps another MSVC version or are you using the borland compiler? I admit C1017 sounds like MSVC. Michiel Salters > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org]On Behalf Of Daniel Lidström > Sent: dinsdag 9 november 2004 14:33 > To: 'boost(a)lists.boost.org' > Subject: [boost] Problem to use boost > > > Hi, > > this is what I've done: > compiled with commandline of > bjam "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET > 2003\Vc7" > "--prefix=C:\projects\boost" install > > Within my project, I've set an additional include path of > C:\projects\boost\include\boost-1_31. Now when I compile my > project with > > one source file containing the line > > #include <boost/shared_ptr.hpp> > > I get this error: > > c:\projects\boost\include\boost-1_31\boost\config\compiler\bor > land.hpp(1 > 3) > : fatal error C1017: invalid integer constant expression > > What have I missed? > > -- > Daniel > _______________________________________________ > 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: Re[4]: [boost] Re: Re: GUI Library Proposal for a Proposal
by Reece Dunn 09 Nov '04

09 Nov '04

Michael Walter wrote: >On Sat, 6 Nov 2004 13:12:14 +0000, Val Samko <boost(a)digiways.com> wrote: > > MW> On Fri, 5 Nov 2004 23:54:30 +0000, Val Samko <boost(a)digiways.com> >wrote: > > >> Once again, in geometry, vector and point are practically the same >thing. > > MW> Not really - you can only represent a point by its radius/position > > MW> vector wrt a given coordinate system. > > > > I thought we are only talking about Cartesian coordinates? Does anyone > > really need a gui library for radial coordinate system? :) >Apologies - I was apparently using the wrong term (not a native >English speaker), and was just seeing "the vector r from the origin to >the current position" on Mathworld. Googling a bit more it appears >that it is such a vector in a polar/spherical coordinate system only. > >The word I was looking for is "Ortsvektor" in German, the vector from >the origin to a certain point. What would be the proper word for that >in English (tried googling, failed :)? "Ort" means place, so it would be "place vector", or more likely "position vector". Is this what you mean? Using http://dictionary.reference.com/translate/text.html produces "radius vector". Regards, Reece _________________________________________________________________ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/

3 2

RE: [boost] Re: logging lib, v1.3
by Kevin Cousins 09 Nov '04

09 Nov '04

Markus Schöpflin wrote" > John Torjo wrote: >> Finally, have had some time to update the logging lib. Get it from: >> http://www.torjo.com/ (of course, it comes packed with docs) > > Just a quick thought that came to my mind... > > Did you consider using the syntax 'BOOST_LOG(dbg, "message" << foobar);' > instead of 'BOOST_LOG(dbg) << "message" << foobar;'? > > While I think the syntax you use looks far nicer, we ususally need the > ability to be able to compile away the logging calls completely and this > only can be done with the first form. ...which introduces the potential for a problem with unintended multiple parameters to the macro function, a la: #define BOOST_LOG(x,y) ... BOOST_LOG(dbg, "message" << templated<1,2>::type() << foobar); // ^BANG! BOOST_LOG(dbg, "message" << ( templated<1,2>::type() ) << foobar); --Kevin. kevin.cousins(a)ir.com _____________________________________________________________________ This email is intended only for the use of the individual or entity named above and may contain information that is confidential and/or privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 9966 1066 and destroy the original message. Thank You _______________________________________________________________________

1 0

library-based property implementation
by Reece Dunn 08 Nov '04

08 Nov '04

Hi All, I have been working on an implementation of a library that allows you to define properties, based on the wg21 N1615 paper by Lois Goldthwaite. The code is committed to the sandbox (under the property directory) with tests and preliminary documentation. I have seperated the properties into two. The boilerplate code for operator overloads, organised by rank, where rank is the number of indices (the term is borrowed from Tensor algebra) provides one group. The other group is the property storage that implements the get and set functions that the boilerplate classes use to implement the operator overloads. : Scalar Properties A scalar property is a single-element property. You can have simple properties that either store their values internally or reference an external data member: class object { int val; public: scalar_property< aliased_property< int > > Val; object(): Val( val ){} }; int main() { scalar_property< value_property< int > > ival( 0 ); ival = 7; ival += 3; int j; scalar_property< aliased_property< int > > jval( j ); jval = 2; assert( j == 2 ); } You can also define more complex properties that use class methods to control them: class object { int val; public: int get_Val() const{ return val; } void set_Val( const int & v ){ val = v; } scalar_property< object_property < int, object, &object::get_Val, &object::set_Val > > Val; object(): Val( this ){} }; : Rank 1 Properties A rank 1 property is a 1-dimensional property. For example: class result_set { public: // property record index[]; record get_record( int i ) const; void set_record( int i, record r ); boost::rank1_property< boost::rank1_object_property < record, int, result_set, &result_set::get_record, &result_set::set_record > > record; public: result_set(): record( this ) { } }; Regards, Reece

2 2