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

Kai C++ for Linux and Solaris
by Wintermantel , Marc 22 Aug '02

22 Aug '02

Hi everybody, We really badly need the latest version available of Kai C++ Compiler for Linux and Solaris. If someone wants to sell his copy, please write me!!! We would really be grateful. Yours truly, Marc Wintermantel Marc Wintermantel IMES - Structures Technology ETH Zurich, LEO C4 Leonhardstrasse 27 CH- 8092 Zurich Tel. ++41 1 633 35 32 Fax. ++41 1 632 17 02 [Non-text portions of this message have been removed]

1 0

boost::object_pool
by wugui 22 Aug '02

22 Aug '02

class A; class B; class AB : virtual public A, virtual public B; all destruct is virtual boost::object_pool<AB> pool_ab; B * pb = pool_ab.constuct(); pool_ab.destroy(pb); // is this right?

1 1

boost lambda library compile error
by khuroth 21 Aug '02

21 Aug '02

I have searched already in this list and the dev list for these MSVC compiler errors, but none of the solutions have worked so far. I have turned off precompiled headers, built clean, tried defining BOOST_NO_MEMBER_TEMPLATES before including "boost/lambda/lambda.hpp" (or "boost/lambda/bind.hpp"), and I still always get this error under Visual C++ 6 SP5 (Win2k Pro SP3), in both the Debug and Release configurations: Deleting intermediate files and output files for project 'dWin - Win32 Release'. --------------------Configuration: dWin - Win32 Release--------------- ----- Compiling... dwin-button.cpp dwin-common-control.cpp dwin-dialog.cpp C:\TMP\BOOST\BOOST_1_28_0\boost/lambda/detail/lambda_fwd.hpp(31) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1794) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information Not sure what I'm doing wrong..

4 6

Boost Concept Check Library
by igor_bashkirov 21 Aug '02

21 Aug '02

Hello, I work on big software project that is ported to several platforms/compilers, including Linux,Solaris/GCC 2.95.2,3.0.4); Windows/MSVC 6.0; AIX/VisualAge; MacOS X / GCC 2.95.2 (Apple). Recently, I decided to make use of Boost library (v 1.28) and the first thing I tried was Boost Concept Check Library (BCCL). Unfortunately, the use of the library wasn't as smooth as I expected, namely, with respect to BOOST_CLASS_REQUIRES macro. Thus, I'd like to submit a couple of observations and one proposal regarding usage of this macro. Let's start with observations: following is the snippet from <boost/concept_check.hpp> header: [code // The BOOST_CLASS_REQUIRES macros use function pointers as // template parameters, which VC++ does not support. #if defined(BOOST_NO_FUNCTION_PTR_TEMPLATE_PARAMETERS) #define BOOST_CLASS_REQUIRES(type_var, concept) .... #else #define BOOST_CLASS_REQUIRES(type_var, concept) \ typedef void (concept <type_var>::* func##type_var##concept)(); \ .... end code] As you could see, BOOST_CLASS_REQUIRES macros evaluate to nothing if BOOST_NO_FUNCTION_PTR_TEMPLATE_PARAMETERS symbol is defined. But, to my great surprise, I didn't find any more references to BOOST_NO_FUNCTION_PTR_TEMPLATE_PARAMETERS symbol throughout the Boost library. Moreover, the above comment about VC++ not supporting function pointers as template parameters is wrong (at least for MSVC 6.0 with SP5). Not to be unfounded, I will provide following sample program successfully compiled and run under MSVC 6.0 with SP5: [code #include <iostream> using namespace std; typedef void(*FP)(); template <FP T> class X { FP fp_; public: X() : fp_(T) {} void print() const { cout << fp_ << endl; } }; void f() {} int main(int, char**) { X<&f> x1; x1.print(); return 0; } end code] The same is true for pointers to member functions of both ordinary and template classes. OK, this observation could be treated as "cosmetic" one, but the following won't. Let's look at the definition of BOOST_CLASS_REQUIRES macro: [code #define BOOST_CLASS_REQUIRES(type_var, concept) \ typedef void (concept <type_var>::* func##type_var##concept)(); \ template <func##type_var##concept _Tp1> \ struct concept_checking_##type_var##concept { }; \ typedef concept_checking_##type_var##concept< \ BOOST_FPTR concept <type_var>::constraints> \ concept_checking_typedef_##type_var##concept end code] and at a typical usage of this macro (taken from Boost documentation): [code template <class T> struct generic_library_class { BOOST_CLASS_REQUIRES(T, EqualityComparableConcept); // ... }; end code] Here, the "EqualityComparableConcept" is a concept checking class defined in the "boost" namespace. OK, that's great and works fine until "generic_library_class" is also declared in the "boost" namespace. Let's now suppose "generic_library_class" is declared in namespace "ns1". Then, BOOST_CLASS_REQUIRES macro evaluates to following: [code namespace ns1 { template <class T> struct generic_library_class { typedef void (EqualityComparableConcept <T>::* funcTEqualityComparableConcept)(); ... }; } end code] Did you see the problem places? Yes, it's where "concept" parameter of the macro is substituted for "EqualityComparableConcept". This name is not declared in the namespace "ns1"! The first itch could be to specify "boost::EqualityComparableConcept" as a value of the second parameter of the macro, but, "not so fast, Skywalker!" - in this case we will end up with "funcTboost::EqualityComparableConcept" name for the pointer to member function that is not a legal name of C/C++ identifier. Someone could say "What a big deal?! Just write 'using namespace boost;' or 'using boost::EqualityComparableConcept;' just before declaring 'generic_library_class'.". Well, the declaration of "generic_library_class" seems to be in the header, right? And what do you think about writing "using-directives" in header files? Yes, right, - it's evil! Especially for large production code. Just check your favorite C++ book. Though, the use of "using-declarations" in headers is a moot point, I also consider it as evil for the same reasons as for "using- directives". Anyway, "using-declarations" won't help us, - they just don't work under MSVC 6.0 in our case. So, what do we have, - "exclusive circle"? I hope not. Finally, I got to the proposal that should help us to eliminate defects of the macro and to obviate above-stated difficulties. What if to add one more parameter, say, "ns", to the BOOST_CLASS_REQUIRES macro to pass the name of the namespace the concept checking class belongs to? Let's look at the new definition of the macro: [code #define BOOST_CLASS_REQUIRES(type_var, ns, concept) \ typedef void (ns::concept <type_var>::* func##type_var##ns##concept) (); \ template <func##type_var##ns##concept _Tp1> \ struct concept_checking_##type_var##ns##concept { }; \ typedef concept_checking_##type_var##ns##concept< \ BOOST_FPTR ns::concept <type_var>::constraints> \ concept_checking_typedef_##type_var##ns##concept; end code] and at it's usage: [code namespace ns1 { template <class T> struct generic_library_class { BOOST_CLASS_REQUIRES(T, boost, EqualityComparableConcept); // ... }; } end code] that will evaluate to the following: [code namespace ns1 { template <class T> struct generic_library_class { typedef void (boost::EqualityComparableConcept <T>::* funcTboostEqualityComparableConcept)(); ... }; } end code] That's it. Moreover, this solution does not suffer from yet another drawback inherent to the original one, viz, name clashing when using in the same class concept checking classes with the same name, but from different namespaces. The only issue I could see with my suggestion was impossibility to use concept checking classes declared at the global scope, but, I hope nobody would think of such thing, because it's evil (sorry for repetition). I hope the proposed solution will increase usability of the BCCL. Best regards, Igor Bashkirov.

3 2

Upgrade VisC++ compiler
by sen_al2002 20 Aug '02

20 Aug '02

Hi, I am a newbie to all this programmer stuff. I am a physics student doing some computer simulations. I was trying to use the special function atanh from boost libraries but couldn't. The error message reads d:\boost_1_28_0\atanh.hpp(77) : error C2989: 'atanh_helper1_t<T,0>' : template class has already been defined as a non-template class Some advised me to update my VisC++ ver 6.0 compiler. How can I do that? Does anybody out there have any better advise? Thanks sen

4 4

boost python link error
by kiminkim 20 Aug '02

20 Aug '02

I want to export C++ class...use boost lib but link error occured... help me. #include <windows.h> #include <boost/python/class_builder.hpp> #include <string> namespace python = boost::python; class CBaseBox { public: CBaseBox() {}; void move(); private: std::string a; }; void CBaseBox::move() { MessageBox(NULL, "kkm", "kkm", MB_OK); } BOOST_PYTHON_MODULE_INIT(tuesday) { python::module_builder this_module("tuesday"); python::class_builder<CBaseBox> CBaseBox_class(this_module, "CBaseBox"); CBaseBox_class.def(&CBaseBox::move , "move"); } --------------------Configuration: tuesday - Win32 Debug-------------------- Compiling... export.cpp Linking... Creating library pyds\./tuesday_d.lib and object pyds\./tuesday_d.exp export.obj : error LNK2001: unresolved external symbol "class CBaseBox & __cdecl from_python(struct _object *,struct boost::python::type<class CBaseBox &>)" (?from_python@@YAAAVCBaseBox@@PAU_object@@U?$type@AAVCBaseBox@@@python@boost @@@Z) pyds\.\tuesday_d.pyd : fatal error LNK1120: 1 unresolved externals Error executing link.exe.

1 0

Boost Python error handling
by cseymour＠interchange.ubc.ca 19 Aug '02

19 Aug '02

Here is a sample program which shows the problem i've been having (posted in earlier messages). When I import the module "sample" and run the function test(), I get the following output: This is a test Raising an error Aborted When I should get a message saying it caught the error, and then a Python error, instead of it Aborting and quitting Python. /* sample.c */ #include "Python.h" #include "boost/python/class_builder.hpp" namespace py = boost::python; void test() { std::cout << "This is a test" << std::endl; std::cout << "Raising an error" << std::endl; PyErr_SetString(PyExc_TypeError, "This is the error"); throw py::argument_error(); } BOOST_PYTHON_MODULE_INIT(sample) { try { py::module_builder this_module("sample"); this_module.def(test, "test"); } catch (...) { std::cout << "Caught an error" << std::endl; py::handle_exception(); } }

1 0

Newbie and shared_ptr
by Ian Mold 19 Aug '02

19 Aug '02

I have been looking at the shared_ptr class, and I have made a change to include an assignment from a standard pointer. I have done this so that I don't have to create a new shared_ptr just to reassign an existing shared_ptr. // Assignment to a 'normal' pointer. shared_ptr & operator=(T * r) { this_type(r).swap(*this); return *this; } I have a few questions. 1) Is this necessary? 2) Does this do the job? 3) Is there any reason this wasn't included in the first place? I welcome any comments. Regards, IanM

3 2

BGL: Loops in undirected graph
by Tarjei Knapstad 19 Aug '02

19 Aug '02

Is there any "standard best way" of detecting loops in an undirected graph? I had a look at chapter 4.2 in the book (which does an implementation for bidirectional graphs), and tried to adapt this implementation, but with no particular luck :) The graph I've set up in my test suite looks like this (I hope my mail prog. doesn't screw up the formatting) H15 | H8 C2 \ / \ H9-C0-C1 C3-O7-H14 / | | H10 C6 C4 / \ / \ H11 C5 H13 | H12 I'm working with molecules, so the letters denote the type of atom, but that's of no importance here. The numbers are the vertex descriptors. What I'm trying to create is an algorithm that will return the set of vertices [1, 2, 3, 4, 5, 6] defining. Now, my first step is (exactly like in the book) to record every back edge in the graph. As my graph is undirected, and there is allways a path from any one vertex to any other vertex, I thought I could just do a DFS from the first vertex in any such graph and record the back edges. In the above example, starting from 'C0', I'd expect the set of back edges obtained from a DFS to be 1-2, 2-3, 3-4, 4-5, 5-6 and 6-1, a total of 6 edges. The actual result obtained however also includes the following edges: 1-0, 11-6, 12-5, 13-4, 7-3, 14-7, 15-2, 8-0, 9-0 and 10-0. Why is this? I'm assuming there's something I missed out on, regarding graph theory and how the basic DFS works, but I cannot see any logic in this. If so, how could I modify my DFS visitor to record the (in my problem domain) "correct" back edges? This problem also gives me further trouble when trying to detect which vertices are part of each cycle. Does any of you have any suggestion for an effective implementation of the "find vertices that are part of each cycle" part of the algorithm? Any help appreciated. Cheers, -- Tarjei Knapstad

2 4

boost::function/bind Usage Again
by Albrecht Fritzsche 19 Aug '02

19 Aug '02

Here I want to extend simple callbacks so that these callbacks take an argument void fun(int i) { std::cout << "Hi fun " << i << std::endl; } struct Foo { void bar(int i) { std::cout << "Hi bar " << i << std::endl; } }; template <class Value> struct CallFunction { CallFunction(const Value& v) : mValue(value) {} // defined outside void operator()(const boost::function<void, Value>& fun) { if (fun) fun(mValue); } const Value& mValue; }; int main() { std::vector< boost::function<void, int> > funs; Foo foo; funs.push_back(&fun); funs.push_back(boost::bind(&Foo::bar, &foo, _1)); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ int value = 7; std::for_each(funs.begin(), funs.end(), CallFunction<int>(value)); return 0; } Is this the right usage of the /_1/ here? This code runs (at least on my machine:-), but I'm quite unsure about this place holder. And since the online docu... Ah, now I see - in the online doc there are some links missing. In the files section not only the bind_template.hpp link refers to that very file but also the arg.hpp and placeholders.hpp links and many more. Having checked now the sources makes not everything clear, but at least clearer. So, I would be happy if anyone could let me know if my usage includes some misuse etc... Thanks Ali

3 2

Using gcc's typeof and boost.lambda together.
by Matthew Dempsky 19 Aug '02

19 Aug '02

I was just playing around with the boost.lambda library and thought of playing a bit with it using gcc's typeof extension... this is the code I used (just slightly modified documentation code): typedef typeof(_1 = 1) assign_one; list<int> v(10); for_each(v.begin(), v.end(), assign_one()); I was hoping it would work the same as the documentation's code, but instead it generates a few big errors about lambda_functor_base<...>::lambda_functor_base() not existing. I know typeof is a gnu extension and it's not really portable to use it in code, but does anyone have any ideas of how to get something like this to work correctly? -jivera

2 1

bug in regex 3.31 (boost 1.28)?
by emarkp 19 Aug '02

19 Aug '02

I sent this originally to James Maddock, but realized this is probably a better place to post it. At work we've been testing out regex (nice work BTW) in some of our code, and appear to have found a bug. We ran into it parsing HTML, and I've written a test C++ app to reproduce it. In the program below, the output should be the same for both searches as far as I can tell, but it's not. I don't know if it's some interaction with the quote character or something like that. We attempted to use other quantifiers (after '?', we tried '*', '{0,1}', ["]?) to no avail. I'm confident this is not user error. The extra grouping is annoying (in "goodPatternStr"), but is an acceptable workaround. The strange thing is that a non-capturing group doesn't fix it. Ideas? --Mark Ping -------------------------------------------------------------------------------------- output: input: <input type="hidden" name="MfcISAPICommand" value="SellYourItem" badOut :<input type="hidden" name="MfcISAPICommand" value="SellYourItem badOutName : badOutValue:SellYourItem goodOut :<input type="hidden" name="MfcISAPICommand" value="SellYourItem goodOutName :MfcISAPICommand goodOutValue:SellYourItem Press any key to continue -------------------------------------------------------------------------------------- #include <iostream> #include <string> #include <boost/regex.hpp> using namespace boost; using namespace std; int main() { const char* badPatternStr = "<input[^>]*name=\"?([^> \"]*)[^>]*value=\"?([^> \"]*)"; const char* goodPatternStr = "<input[^>]*name=(\"?)([^> \"]*)[^>]*value=\"?([^> \"]*)"; // ^^^^^ //note that the only difference between bad and good is that "good" //has grouping around the optional " after 'name=' // //In both versions of the matches, the second group is matched. //Only the first group has this problem. boost::match_results<std::string::const_iterator> what; std::string in = "<input type=\"hidden\" name=\"MfcISAPICommand\" value=\"SellYourItem\""; std::string::const_iterator start, end; start = in.begin(); end = in.end(); unsigned int flags = boost::match_default; std::string badOut, badOutName, badOutValue; if(regex_search(start, end, what, regex(badPatternStr), flags)) { badOut = what[0]; int numGroups = what.size(); // name badOutName = what[1]; badOutValue = what[2]; } std::string goodOut, goodOutName, goodOutValue; if(regex_search(start, end, what, regex(goodPatternStr), flags)) { goodOut = what[0]; int numGroups = what.size(); // name goodOutName = what[2]; goodOutValue = what[3]; } cout << "input: "; cout << in << endl << endl; cout << "badOut :" << badOut << endl; cout << "badOutName :" << badOutName << endl; cout << "badOutValue:" << badOutValue << endl; cout << endl; cout << "goodOut :" << goodOut << endl; cout << "goodOutName :" << goodOutName << endl; cout << "goodOutValue:" << goodOutValue << endl; return 0; }

2 5

RE: [Boost-Users] detail/lightweight_mutex.hpp
by Tom Matelich 17 Aug '02

17 Aug '02

> From: Tom Matelich [mailto:tmatelich@zetec.com] > > From: Peter Dimov [mailto:pdimov@mmltd.net] > > From: "Tom Matelich" <tmatelich(a)zetec.com> > > > I'm attempting to go to Boost 1.28 on our HPUX 10.20 boxes. > > I've run into > > a > > > problem with an assumption about the type of pthread_mutexattr_t. > > > detail\lwm_pthreads.hpp calls: > > > > > > pthread_mutex_init(&m_, 0); > > > > > > HP's pthread.h (10.20 uses DCE) has that defined as: > > > > > > int pthread_mutex_init (pthread_mutex_t *,pthread_mutexattr_t); > > > > I don't know what to do about it. My POSIX draft says > > > > int pthread_mutex_init(pthread_mutex_t *restrict mutex, const > > pthread_mutexattr_t *restrict attr); > > > > and goes on to specify that 0/NULL for the second argument > > causes default > > attributes to be used. > > > > I know little - if anything - about HPUX 10.20; if you find a > > solution let > > me know, and I'll incorporate it into lwm_pthreads.hpp. Sorry. > > > > The dce documentation I see says to use pthread_mutexattr_default. > http://www.transarc.ibm.com/Library/documentation/dce/1.1/pthread_mutex_init .html > >So, it looks like I need to find a version to if or ifdef off of. I found a define in dce/cma.h (appended to my original email) which seems to fit the bill: /* * Define a symbol which client code can test to determine whether the * underlying threads package is DECthreads or not. This is especially * important to clients of the Pthreads interface who may want to use * certain DECthreads extensions, such as the global lock and non-real-time * scheduling policies, on the DECthreads platform while maintaining * portability to a "vanilla" pthreads implementation. */ #define _DECTHREADS_ 1 Although, I'm not sure how to find out if this should be used generally, or only on HP. ----------------------------------------------------------------------- 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

regex performance
by Paul Dubuc 17 Aug '02

17 Aug '02

I'm doing some performance comparisons between Rogue Wave's Regexp class (http://www.roguewave.com/support/docs/tlsref/rwcregexp.cfm) and boost::regex using simple expressions like "^metal.*" and "[0-9]+" with regex_search(). regex is slower by a factor of 6, measuring cpu time (on a SunBlade 100 runing Solaris 8). Is there anything I can do to speed it up? I tried using different values of boost::regbase::flag_type_ to adjust how the regular expressions are interpreted, but with little effect. Any other ideas? (I'm using boost_1_27_0.) Thanks, -- Paul M. Dubuc

7 12

request for comment on possible submission to library
by DrXenos 17 Aug '02

17 Aug '02

I was wondering if anyone would be interested in a Set Library, similar to Pascal's set type for ordinal types. I want to make sure someone would fine it useful (and not trivial, done-to-death, etc.) before I take the time to "Boostify" it and get a release from my employer. A while ago I needed a set type that was compact, fast, and avoided heap allocation. The number of elements was constant for a particular set type, and the element type could be any integral type (primarily enums). Similar types from STL are set, vector<bool>, and bitset, but none quite suited the application. My set type (Set) stores elements at the bit level, like vector<bool> and bitset, but it allows the creation of compile-time set constants. Also, with a good optimizing compiler, operations on constant sets will be done at compile-time, though as of yet, there is no direct support for guaranteeing this in the code. The class provides the usual set operations. For efficiency, set operations are done in parallel groups of the machine's word size. So, set types whose max. number of elements is less than or equal to the machine's word size, will have most of its operations done in constant time (usually one machine instruction per operation). Sets whose max. number of elements is greater than the machine's word size will be done in linear time, usually in E / Wb cycles, where E is the max. number of elements and Wb is the machine's word size in bits. Though, with a good compile (through inlining and loop unrolling), this linear time would only be E / Wb instructions. On an average 32-bit processor, that's just 8 instructions to perform the union or intersection of a set of 256 elements. Originally, I avoided loops and used metatemplates to inline the operations, but this resulted in very long compile-times without any gains in performance! And sometimes it resulted in worse performance. That will teach me not to try and second guess today's optimizing compilers! As I stated above, the class template may be instantiated with any integral type, but it was primarily meant for enumerations with will give you the added bonuses of type-safely and symbolic names for the elements. The class assumes that the range given is not disjoint (i.e., 0-63 and not 0 - 16, 19, 63). You may use disjoint ranges, but your sets will contain wasted space. The only requirement is that the range of values is greater than or equal to zero, and that the element type has a representation for -1 (used as a (hidden) sentinel in argument lists of elements). You could even conceivably use a class that was "castable" to int. For example: // element type enum Color {red, orange, yellow, green, blue, violet, NumColors, NilColor = -1}; // type for set of colors typedef Set<Color, NumColors> ColorSet; // set constant const ColorSet rgb = ColorSet::SetOf<red, green, blue>::value(); // this is done at compile-time void foo() { // construction ColorSet s = ColorSet::SetOf<orange, yellow, violet>::value(); // this is done at compile-time ColorSet s1 = ColorSet(a); // this *may* be at compile-time ColorSet s2 = ColorSet(orange, yellow, violet); // this is NOT done at compile-time // (but allows non-constant elements) // operations, some of which *may* be done at compile-time by a smart compiler ColorSet a = s; // assignment ColorSet b = s + rgb; // union ColorSet c = s * rgb; // intersection ColorSet d = s - rgb; // difference ColorSet e = s / rgb; // symmetric difference bool b1 = s == rgb; // equality bool b1 = s != rgb; // unequality bool b3 = s >= rgb; // superset bool b4 = s > rgb; // proper superset bool b5 = s < rgb; // subset bool b6 = s > rgb; // proper subset if (b.contains(red)) // test for set membership std::cout << "b contains the element red" << std::endl; if (red == b) // same as above. can anyone suggest a better operator? // maybe use red -> b and use NULL for false? // or maybe remove and just use b.contains(red)? std::cout << "b contains the element red" << std::endl; } What do you think? Thanks, Rich (spamjunk(a)stny.rr.com)

1 0

RE: [Boost-Users] detail/lightweight_mutex.hpp
by Tom Matelich 16 Aug '02

16 Aug '02

> From: Peter Dimov [mailto:pdimov@mmltd.net] > > From: "Tom Matelich" <tmatelich(a)zetec.com> > > I'm attempting to go to Boost 1.28 on our HPUX 10.20 boxes. > I've run into > a > > problem with an assumption about the type of pthread_mutexattr_t. > > detail\lwm_pthreads.hpp calls: > > > > pthread_mutex_init(&m_, 0); > > > > HP's pthread.h (10.20 uses DCE) has that defined as: > > > > int pthread_mutex_init (pthread_mutex_t *,pthread_mutexattr_t); > > I don't know what to do about it. My POSIX draft says > > int pthread_mutex_init(pthread_mutex_t *restrict mutex, const > pthread_mutexattr_t *restrict attr); > > and goes on to specify that 0/NULL for the second argument > causes default > attributes to be used. > > I know little - if anything - about HPUX 10.20; if you find a > solution let > me know, and I'll incorporate it into lwm_pthreads.hpp. Sorry. > The dce documentation I see says to use pthread_mutexattr_default. http://www.transarc.ibm.com/Library/documentation/dce/1.1/pthread_mutex_init .html So, it looks like I need to find a version to if or ifdef off of. ----------------------------------------------------------------------- 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. -----------------------------------------------------------------------

1 0

detail/lightweight_mutex.hpp
by Tom Matelich 16 Aug '02

16 Aug '02

I'm attempting to go to Boost 1.28 on our HPUX 10.20 boxes. I've run into a problem with an assumption about the type of pthread_mutexattr_t. detail\lwm_pthreads.hpp calls: pthread_mutex_init(&m_, 0); HP's pthread.h (10.20 uses DCE) has that defined as: int pthread_mutex_init (pthread_mutex_t *,pthread_mutexattr_t); after tracing the typedef's down to <dce/cma.h>, I found pthread_mutexattr_t is this: typedef struct CMA_T_HANDLE { cma_t_address field1; short int field2; short int field3; } cma_t_handle; where cma_t_address is a void*. The error message is: .../boost/detail/lwm_pthreads.hpp: In method `boost::detail::lightweight_mutex::lightweight_mutex()': .../boost/detail/lwm_pthreads.hpp:40: conversion from `int' to non-scalar type `CMA_T_HANDLE' requested I'm not sure what solution to use here. Ifdefs are troublesome because it is hard to distinguish between HP 10.x and 11.x, which use different threading models. I don't know a lot about threads on HP, we use ACE so that we don't have to. One thing I do remember is that they conform to a fairly old revision of POSIX. I think attachments are prohibited on this list, so I will append pthread.h and dce/cma.h below. Thanks for your help, Tom <"pthread.h"> /* * (c) Copyright 1990, 1991, 1992, 1993 OPEN SOFTWARE FOUNDATION, INC. * ALL RIGHTS RESERVED * COPYRIGHT NOTICE * Copyright (c) 1990, 1991, 1992, 1993, 1994 Open Software Foundation, Inc. * ALL RIGHTS RESERVED (DCE). See the file named COPYRIGHT.DCE for * the full copyright text. */ /* * @(#)HP DCE/9000 1.5 * @(#)Module: pthread.h $Revision: /main/HPDCE02/5 $ $Date: 1995/07/11 17:25 UTC $ */ /* */ /* * %W% (DEC OSF/1) %G% */ /* * Copyright (c) 1990, 1992 by * Digital Equipment Corporation, Maynard Massachusetts. * All rights reserved. * * This software is furnished under a license and may be used and copied * only in accordance with the terms of such license and with the * inclusion of the above copyright notice. This software or any other * copies thereof may not be provided or otherwise made available to any * other person. No title to and ownership of the software is hereby * transferred. * * The information in this software is subject to change without notice * and should not be construed as a commitment by DIGITAL Equipment * Corporation. * * DIGITAL assumes no responsibility for the use or reliability of its * software on equipment which is not supplied by DIGITAL. */ /* * FACILITY: * * Common Multithread Architecture (CMA) services; POSIX 1003.4 interface * * ABSTRACT: * * External definitions for CMA's pthreads services * * AUTHORS: * * Dave Butenhof * * CREATION DATE: * * 20 February 1990 * * MODIFIED BY: * * Dave Butenhof * Paul Curtin * Webb Scales */ #ifndef PTHREAD #define PTHREAD #if !defined(__STDC__) && defined(_CMA_HP_INT_NONANSI) # include <dce/pthread_int.h> #else #ifdef vms # include <cma.h> #else# include <dce/cma.h> # include <signal.h> #endif #ifdef __cplusplus extern "C" { #endif /* * The implementation makes these basic decisions */ #ifndef _POSIX_THREADS # define _POSIX_THREADS #endif#ifndef _POSIX_THREAD_ATTR_STACKSIZE # define _POSIX_THREAD_ATTR_STACKSIZE #endif#if _CMA_KTHREADS_ != _CMA__MACH # define _POSIX_THREADS_REALTIME_SCHEDULING 1 #else#if defined (_POSIX_THREADS_REALTIME_SCHEDULING) # undef _POSIX_THREADS_REALTIME_SCHEDULING #endif#endif#ifndef _POSIX_THREADS_PER_PROCESS_SIGNALS_1 # define _POSIX_THREADS_PER_PROCESS_SIGNALS_1 1 #endif /* * Implement push and pop for cancellation handlers, using TRY and ENDTRY */ #define pthread_cleanup_push(routine,arg) \ { \ pthread_cleanup_t _XXX_proc = (pthread_cleanup_t)(routine); \ pthread_addr_t _XXX_arg = (arg); \ int _XXX_completed = 0; \ TRY { #define pthread_cleanup_pop(execute) \ _XXX_completed = 1;} \ FINALLY { \ int _XXX_execute = execute; \ if ((! _XXX_completed) || (_XXX_execute)) _XXX_proc (_XXX_arg);} \ ENDTRY} #define pthread_equal_np(thread1,thread2) \ (((thread1).field1 == (thread2).field1) \ && ((thread1).field2 == (thread2).field2) \ && ((thread1).field3 == (thread2).field3)) #define pthread_equal(thread1,thread2) \ (((thread1).field1 == (thread2).field1) \ && ((thread1).field2 == (thread2).field2) \ && ((thread1).field3 == (thread2).field3)) #define pthread_getunique_np(handle) \ ((unsigned int)((pthread_t *)handle)->field2) /* * Sample decisions for the environment types */ typedef cma_t_key pthread_key_t; typedef cma_t_address pthread_addr_t; /* * For compatibility with OSF/1 pthreads */ typedef pthread_addr_t any_t; typedef void (*pthread_cleanup_t) (pthread_addr_t); /* * Sample decision for a one-time initialization control block and its * initialization macro. * * Declare a one time initialization control block as: * * static pthread_once_t block = pthread_once_init; */ typedef cma_t_once pthread_once_t; #define pthread_once_init cma_once_init #define CANCEL_ON 1 #define CANCEL_OFF 0 /* * The following are the portable pthread definitions */ /* * Operations on Handles */ /* * Operations on attributes objects */ typedef cma_t_attr pthread_attr_t; /* * An attributes object is created to specify the attributes of other CMA * objects that will be created. */ int pthread_attr_create (pthread_attr_t *); /* * An attributes object can be deleted when it is no longer needed. */ int pthread_attr_delete (pthread_attr_t *); /* * Operations on threads */ typedef cma_t_thread pthread_t; typedef cma_t_start_routine pthread_startroutine_t; /* * For compatibility with OSF/1 pthreads */ typedef pthread_startroutine_t pthread_func_t; #define PTHREAD_INHERIT_SCHED ((int)cma_c_sched_inherit) #define PTHREAD_DEFAULT_SCHED ((int)cma_c_sched_use_default) #define SCHED_FIFO ((int)cma_c_sched_fifo) #define SCHED_RR ((int)cma_c_sched_rr) #define SCHED_FG_NP ((int)cma_c_sched_throughput) #define SCHED_BG_NP ((int)cma_c_sched_background) /* For compatibility with namespace collision due to POSIX.4 includes */ #ifndef _SYS_SCHED_INCLUDED # define SCHED_OTHER ((int)cma_c_sched_throughput) #endif #define PRI_FIFO_MIN ((int)cma_c_prio_fifo_min) #define PRI_FIFO_MAX ((int)cma_c_prio_fifo_max) #define PRI_RR_MIN ((int)cma_c_prio_rr_min) #define PRI_RR_MAX ((int)cma_c_prio_rr_max) #define PRI_FG_MIN_NP ((int)cma_c_prio_through_min) #define PRI_FG_MAX_NP ((int)cma_c_prio_through_max) #define PRI_BG_MIN_NP ((int)cma_c_prio_back_min) #define PRI_BG_MAX_NP ((int)cma_c_prio_back_max) #define PRI_OTHER_MIN ((int)cma_c_prio_through_min) #define PRI_OTHER_MAX ((int)cma_c_prio_through_max) /* * Operations to define thread creation attributes */ /* * Set or obtain the default thread priority. */ int pthread_attr_setprio (pthread_attr_t *,int); int pthread_attr_getprio (pthread_attr_t); /* * Set or obtain the default scheduling algorithm */ int pthread_attr_setsched (pthread_attr_t *,int); int pthread_attr_getsched (pthread_attr_t); /* * Set or obtain whether a thread will use the default scheduling attributes, * or inherit them from the creating thread. */ int pthread_attr_setinheritsched (pthread_attr_t *,int); int pthread_attr_getinheritsched (pthread_attr_t); /* * Set or obtain the default stack size */ int pthread_attr_setstacksize (pthread_attr_t *,long); long pthread_attr_getstacksize (pthread_attr_t); /* * Set or obtain the default guard size */ int pthread_attr_setguardsize_np (pthread_attr_t *,long); long pthread_attr_getguardsize_np (pthread_attr_t); /* * The following procedures can be used to control thread creation, * termination and deletion. */ /* * To create a thread object and runnable thread, a routine must be specified * as the new thread's start routine. An argument may be passed to this * routine, as an untyped address; an untyped address may also be returned as * the routine's value. An attributes object may be used to specify details * about the kind of thread being created. */ int pthread_create (pthread_t *,pthread_attr_t,pthread_startroutine_t,pthread_addr_t); /* * A thread object may be "detached" to specify that the return value and * completion status will not be requested. */ int pthread_detach (pthread_t *); /* * A thread may terminate it's own execution. */ void pthread_exit (pthread_addr_t); /* * A thread can await termination of another thread and retrieve the return * value of the thread. */ int pthread_join (pthread_t,pthread_addr_t *); /* * Thread Scheduling Operations */ /* * The current user_assigned priority of a thread can be changed. */ int pthread_setprio (pthread_t,int); /* * The current user_assigned scheduler algorithm of a thread can be changed. */ int pthread_setscheduler (pthread_t,int,int); /* * A thread may tell the scheduler that its processor can be made available. */ void pthread_yield (void); /* * Thread Information Operations */ /* * A thread may obtain a copy of its own thread handle. */ pthread_t pthread_self (void); /* * The current user_assigned priority of a thread can be read. */ int pthread_getprio (pthread_t); /* * The current user_assigned scheduler algorithm of a thread can be read. */ int pthread_getscheduler ( pthread_t); /* * Operations on Mutexes */ #define MUTEX_FAST_NP 0 #define MUTEX_RECURSIVE_NP 1 #define MUTEX_NONRECURSIVE_NP 2 typedef cma_t_attr pthread_mutexattr_t; typedef cma_t_mutex pthread_mutex_t; int pthread_mutexattr_create (pthread_mutexattr_t *); int pthread_mutexattr_delete (pthread_mutexattr_t *); int pthread_mutexattr_setkind_np (pthread_mutexattr_t *,int); int pthread_mutexattr_getkind_np (pthread_mutexattr_t); /* * The following routines create, delete, lock and unlock mutexes. */ int pthread_mutex_init (pthread_mutex_t *,pthread_mutexattr_t); int pthread_mutex_destroy (pthread_mutex_t *); int pthread_mutex_lock (pthread_mutex_t *); int pthread_mutex_trylock (pthread_mutex_t *); int pthread_mutex_unlock (pthread_mutex_t *); /* * Operations on condition variables */ typedef cma_t_attr pthread_condattr_t; typedef cma_t_cond pthread_cond_t; int pthread_condattr_create (pthread_condattr_t *); int pthread_condattr_delete (pthread_condattr_t *); /* * A thread can create and delete condition variables. */ int pthread_cond_init (pthread_cond_t *,pthread_condattr_t); int pthread_cond_destroy (pthread_cond_t *); /* * A thread can signal to and broadcast on a condition variable. */ int pthread_cond_broadcast (pthread_cond_t *); int pthread_cond_signal (pthread_cond_t *); int pthread_cond_signal_int_np (pthread_cond_t *); /* * A thread can wait for a condition variable to be signalled or broadcast. */ int pthread_cond_wait (pthread_cond_t *,pthread_mutex_t *); /* * Operations for timed waiting */ /* * A thread can perform a timed wait on a condition variable. */ int pthread_cond_timedwait (pthread_cond_t *,pthread_mutex_t *,struct timespec *); /* * Operations for client initialization. */ typedef void (*pthread_initroutine_t) (void); int pthread_once (pthread_once_t *,pthread_initroutine_t); /* * Operations for per-thread context */ typedef cma_t_destructor pthread_destructor_t; /* * A unique per-thread context key can be obtained for the process */ int pthread_keycreate (pthread_key_t *,pthread_destructor_t); /* * A thread can set a per-thread context value identified by a key. */ int pthread_setspecific (pthread_key_t,pthread_addr_t); /* * A thread can retrieve a per-thread context value identified by a key. */ int pthread_getspecific (pthread_key_t,pthread_addr_t *); /* * Operations for alerts. */ /* * The current thread can request that a thread terminate it's execution. */ int pthread_cancel (pthread_t); /* * The current thread can poll for alert delivery. */ void pthread_testcancel (void); /* * The current thread can enable or disable alert delivery (PTHREAD * "cancels"); it can control "general cancelability" (CMA "defer") or * just "asynchronous cancelability" (CMA "asynch disable"). */ int pthread_setasynccancel (int); int pthread_setcancel (int); _CMA_IMPORT_ pthread_attr_t pthread_attr_default; _CMA_IMPORT_ pthread_mutexattr_t pthread_mutexattr_default; _CMA_IMPORT_ pthread_condattr_t pthread_condattr_default; /* * Define nonportable extensions */ extern int pthread_get_expiration_np (struct timespec *,struct timespec *); extern int pthread_delay_np (struct timespec *); #if (_CMA_UNIX_TYPE == _CMA__SVR4) extern unsigned int pthread_delay_unsigned_np (unsigned int ); #endif /* (_CMA_UNIX_TYPE == _CMA__SVR4) */ extern void pthread_lock_global_np (void); extern void pthread_unlock_global_np (void); # if _CMA_OS_ != _CMA__VMS extern int pthread_signal_to_cancel_np (sigset_t *,pthread_t *); # endif #ifdef __hpux extern int pthread_is_multithreaded_np (void); #endif #ifdef __cplusplus } #endif #endif /* _CMA_HP_INT_NONANSI */ #endif </"pthread.h"> <"dce/cma.h"> /* * (c) Copyright 1990, 1991, 1992, 1993 OPEN SOFTWARE FOUNDATION, INC. * ALL RIGHTS RESERVED * COPYRIGHT NOTICE * Copyright (c) 1990, 1991, 1992, 1993, 1994 Open Software Foundation, Inc. * ALL RIGHTS RESERVED (DCE). See the file named COPYRIGHT.DCE for * the full copyright text. * * (c) Copyright 1991, 1992 Siemens-Nixdorf Information Systems * Burlington, MA, USA */ /* * @(#)HP DCE/9000 1.5 * @(#)Module: cma.h $Revision: /main/HPDCE02/3 $ $Date: 1995/09/07 19:35 UTC $ */ /* */ /* * %W% (DEC OSF/1) %G% */ /* * Copyright (c) 1988, 1992 by * Digital Equipment Corporation, Maynard Massachusetts. * All rights reserved. * * This software is furnished under a license and may be used and copied * only in accordance with the terms of such license and with the * inclusion of the above copyright notice. This software or any other * copies thereof may not be provided or otherwise made available to any * other person. No title to and ownership of the software is hereby * transferred. * * The information in this software is subject to change without notice * and should not be construed as a commitment by DIGITAL Equipment * Corporation. * * DIGITAL assumes no responsibility for the use or reliability of its * software on equipment which is not supplied by DIGITAL. */ /* * FACILITY: * * Digital's Proprietary Interface to DECthreads (CMA) * * ABSTRACT: * * External definitions for CMA services * * AUTHORS: * * Dave Butenhof * * CREATION DATE: * * 2 November 1988 * * MODIFIED BY: * * Dave Butenhof * Bob Conti * Paul Curtin * Hans Oser * Webb Scales */ #ifndef CMA_INCLUDE #define CMA_INCLUDE /* * Define a symbol which client code can test to determine whether the * underlying threads package is DECthreads or not. This is especially * important to clients of the Pthreads interface who may want to use * certain DECthreads extensions, such as the global lock and non-real-time * scheduling policies, on the DECthreads platform while maintaining * portability to a "vanilla" pthreads implementation. */ #define _DECTHREADS_ 1 /* * The implementation makes these basic decisions */ #if defined(vms) || defined(__vms) || defined (VMS) || defined(__VMS) || defined(__vms__) # include <cma_config.h> /* configuration symbols */ #else# include <dce/cma_config.h> /* configuration symbols */ #endif /* For HP_UX, specifies which version of the operating system we are building on */ #if _CMA_VENDOR_ == _CMA__HP # include <dce/hpdce_platform.h> #endif /* Fix ordering problem with "wait" definition in HP-UX 1010 header files */ #if defined(__hpux1010p) # define wait cma_wait #endif #if (_CMA_UNIX_TYPE == _CMA__SVR4) && (_CMA_REENTRANT_CLIB_) # if defined _libcma_code_ # include <cma_libc_redefs.h> # endif#endif #if _CMA_OS_ != _CMA__VMS # include <sys/types.h> # include <sys/time.h> #endif #if _CMA_OS_ == _CMA__VMS # include <exc_handling.h> /* Bring in exception services */ #else# include <dce/exc_handling.h> /* Bring in exception services */ #endif #if (_CMA_OSIMPL_ == _CMA__OS_OSF) && _CMA_REENTRANT_CLIB_ # define _REENTRANT 1 /* Enable reentrant errno.h */ #endif #if (_CMA_VENDOR_ == _CMA__HP) && _CMA_REENTRANT_CLIB_ # ifndef _REENTRANT # define _REENTRANT 1 # endif#endif #ifdef __cplusplus extern "C" { #endif /* * Sample decisions for the environment types */ typedef int cma_t_integer; typedef unsigned int cma_t_boolean; typedef unsigned int cma_t_natural; typedef float cma_t_interval; typedef int cma_t_key; typedef int cma_t_status; typedef int cma_t_priority; #if _CMA_VOID_ typedef void *cma_t_address; #elsetypedef char *cma_t_address; #endif #define cma_c_false (cma_t_boolean)0 #define cma_c_true (cma_t_boolean)1 #define cma_c_null_ptr (cma_t_address)0 #define cma_c_prio_fifo_min 16 #define cma_c_prio_fifo_mid 24 #define cma_c_prio_fifo_max 31 #define cma_c_prio_rr_min 16 #define cma_c_prio_rr_mid 24 #define cma_c_prio_rr_max 31 #define cma_c_prio_through_min 8 #define cma_c_prio_through_mid 12 #define cma_c_prio_through_max 15 #define cma_c_prio_back_min 1 #define cma_c_prio_back_mid 4 #define cma_c_prio_back_max 7 #define cma_c_prio_ada_low_min 0 #define cma_c_prio_ada_low_mid 4 #define cma_c_prio_ada_low_max 7 /* * The implementation of the cma_t_date_time type should match the "native * time" of the platform: that allows clients to use the full set of platform * time operations, rather than just "cma_get_expiration", to compute and * test timed waits. * * This section assumes the platform is either "VMS" or "UNIX-ish". Others * will require changes. */ #if _CMA_OS_ == _CMA__VMS typedef struct CMA_T_DATE_TIME { unsigned long int low; unsigned long int high; } cma_t_date_time; #elsetypedef struct timeval cma_t_date_time; #endif #ifdef __hpux /* * Structure for C++ callbacks */ typedef struct CB_STRUCT { void (*start)(); void (*end)(); void (*out)(); void (*in)(); } _ctxcb_spec_t; #endif /* * Sample decisions for what handles shall be */ typedef struct CMA_T_HANDLE { cma_t_address field1; short int field2; short int field3; } cma_t_handle; #define cma_thread_get_unique(handle) \ ((unsigned int)((cma_t_thread *)handle)->field2) #define cma_c_handle_size sizeof(cma_t_handle) typedef cma_t_handle cma_t_mutex; /* Needed for CMA_ONCE_BLOCK */ /* * Predefined null handle */ #ifndef _CMA_SUPPRESS_EXTERNALS_ _CMA_IMPORT_ cma_t_handle cma_c_null; #endif /* * Sample decision for a one-time initialization control block and its * initialization macro. * * Declare a one time initialization control block as: * * static cma_t_once block = cma_once_init; */ typedef struct CMA_T_ONCE { cma_t_integer field1; cma_t_integer field2; cma_t_integer field3; } cma_t_once; #define cma_once_init {0, 0, 0} /* * Sample decision for a variable to save the current alert state. */ typedef struct CMA_T_ALERT_STATE { cma_t_integer state1; cma_t_integer state2; } cma_t_alert_state; /* * The following are the portable CMA definitions */ /* * Operations on Handles */ /* * The value of a handle can be assigned the value of another handle. */ extern void cma_handle_assign (cma_t_handle *, cma_t_handle *); /* * The value of a handle can be compared to the value of another handle. */ extern cma_t_boolean cma_handle_equal ( cma_t_handle *, cma_t_handle *); /* * Operations on attributes objects */ typedef cma_t_handle cma_t_attr; /* * An attributes object is created to specify the attributes of other CMA * objects that will be created. */ extern void cma_attr_create (cma_t_attr *,cma_t_attr *); /* * An attributes object can be deleted when it is no longer needed. */ extern void cma_attr_delete (cma_t_attr *); /* * Operations on threads */ typedef cma_t_handle cma_t_thread; typedef cma_t_address (*cma_t_start_routine) (cma_t_address); typedef enum CMA_T_EXIT_STATUS { cma_c_term_error = 0, cma_c_term_normal = 1, cma_c_term_alert = 2 } cma_t_exit_status; typedef enum CMA_T_SCHED_INHERIT { cma_c_sched_inherit = 0, cma_c_sched_use_default = 1 } cma_t_sched_inherit; typedef enum CMA_T_SCHED_POLICY { cma_c_sched_fifo = 0, cma_c_sched_rr = 1, cma_c_sched_throughput = 2, cma_c_sched_background = 3, cma_c_sched_ada_low = 4 } cma_t_sched_policy; #define cma_c_sched_default cma_c_sched_throughput #define cma_c_sched_other cma_c_sched_default /* * The following procedures can be used to control thread creation, * termination and deletion. */ /* * To create a thread object and runnable thread, a routine must be specified * as the new thread's start routine. An argument may be passed to this * routine, as an untyped address; an untyped address may also be returned as * the routine's value. An attributes object may be used to specify details * about the kind of thread being created. */ extern void cma_thread_create (cma_t_thread *,cma_t_attr *,cma_t_start_routine,cma_t_address); /* * A thread object may be "detached" to specify that the return value and * completion status will not be requested. */ extern void cma_thread_detach (cma_t_thread *); /* * A thread may terminate it's own execution. */ extern void cma_thread_exit_error (void); extern void cma_thread_exit_normal (cma_t_address); /* * A thread can await termination of another thread and retrieve the return * value and completion status of the thread. */ extern void cma_thread_join (cma_t_thread *,cma_t_exit_status *,cma_t_address *); /* * Operations to define thread creation attributes */ /* * Set or obtain the default thread priority. */ extern void cma_attr_set_priority (cma_t_attr *,cma_t_priority); extern void cma_attr_get_priority (cma_t_attr *,cma_t_priority *); /* * Set or obtain the default scheduling algorithm */ extern void cma_attr_set_sched (cma_t_attr *,cma_t_sched_policy ,cma_t_priority); extern void cma_attr_get_sched (cma_t_attr *,cma_t_sched_policy *); /* * Set or obtain whether a thread will use the default scheduling attributes, * or inherit them from the creating thread. */ extern void cma_attr_set_inherit_sched (cma_t_attr *,cma_t_sched_inherit); extern void cma_attr_get_inherit_sched (cma_t_attr *,cma_t_sched_inherit *); /* * Set or obtain the default stack size */ extern void cma_attr_set_stacksize (cma_t_attr *,cma_t_natural); extern void cma_attr_get_stacksize (cma_t_attr *,cma_t_natural *); /* * Set or obtain the default guard size */ extern void cma_attr_set_guardsize (cma_t_attr *,cma_t_natural); extern void cma_attr_get_guardsize (cma_t_attr *,cma_t_natural *); /* * Thread Scheduling Operations */ /* * The current user_assigned priority of a thread can be changed. */ extern void cma_thread_set_priority (cma_t_thread *,cma_t_priority); /* * The current user_assigned scheduler algorithm of a thread can be changed. */ extern void cma_thread_set_sched (cma_t_thread *,cma_t_sched_policy,cma_t_priority); /* * A thread may tell the scheduler that its processor can be made available. */ extern void cma_yield (void); #ifndef _HP_CMA_PERF_ extern void cma_yield_noselect (void); #endif /* _HP_CMA_PERF_ */ /* * A thread may enter a wait state for a speciifed period of time. */ extern void cma_delay (cma_t_interval); /* * Thread Information Operations */ /* * A thread may obtain a copy of its own thread handle. */ extern void cma_thread_get_self (cma_t_thread *); /* * The current user_assigned priority of a thread can be read. */ extern void cma_thread_get_priority (cma_t_thread *,cma_t_priority *); /* * The current user_assigned scheduler algorithm of a thread can be read. */ extern void cma_thread_get_sched (cma_t_thread *,cma_t_sched_policy *); /* * Operations on Mutexes */ typedef enum CMA_T_MUTEX_KIND { cma_c_mutex_fast = 0, cma_c_mutex_recursive = 1, cma_c_mutex_nonrecursive = 2 } cma_t_mutex_kind; /* * Operations to define mutex creation attributes */ /* * Set or obtain whether mutex locks can nest. */ extern void cma_attr_set_mutex_kind (cma_t_attr *,cma_t_mutex_kind); extern void cma_attr_get_mutex_kind (cma_t_attr*,cma_t_mutex_kind *); /* * The following routines create, delete, lock and unlock mutexes. */ extern void cma_mutex_create (cma_t_mutex *,cma_t_attr *); extern void cma_mutex_delete (cma_t_mutex *); extern void cma_mutex_lock (cma_t_mutex *); extern cma_t_boolean cma_mutex_try_lock (cma_t_mutex *); extern void cma_mutex_unlock (cma_t_mutex *); extern void cma_lock_global (void); extern void cma_unlock_global (void); /* * Operations on condition variables */ typedef cma_t_handle cma_t_cond; /* * A thread can create and delete condition variables. */ extern void cma_cond_create (cma_t_cond *,cma_t_attr *); extern void cma_cond_delete (cma_t_cond *); /* * A thread can signal to and broadcast on a condition variable. */ extern void cma_cond_broadcast (cma_t_cond *); extern void cma_cond_signal (cma_t_cond *); extern void cma_cond_signal_int (cma_t_cond *); /* * A thread can wait for a condition variable to be signalled or broadcast. */ extern void cma_cond_wait (cma_t_cond *,cma_t_mutex *); /* * Operations for timed waiting */ /* * A thread can perform a timed wait on a condition variable. */ extern cma_t_status cma_cond_timed_wait (cma_t_cond *,cma_t_mutex *,cma_t_date_time *); /* * A thread may perform some operations on absolute date-time and intervals. */ extern void cma_time_get_expiration (cma_t_date_time *,cma_t_interval ); /* * Operations for CMA and client initialization. */ /* * Initialize the CMA facility. */ extern void cma_init (void); /* * A thread can declare a one-time initialization routine. The address of * the init block and routine are passed as parameters. */ typedef void (*cma_t_init_routine) (cma_t_address); extern void cma_once (cma_t_once *_block,cma_t_init_routine,cma_t_address); /* * Operations for per-thread context */ typedef void (*cma_t_destructor) (cma_t_address); /* * A unique per-thread context key can be obtained for the process */ extern void cma_key_create (cma_t_key *,cma_t_attr *,cma_t_destructor); /* * A thread can set a per-thread context value identified by a key. */ extern void cma_key_set_context (cma_t_key,cma_t_address); /* * A thread can retrieve a per-thread context value identified by a key. */ extern void cma_key_get_context (cma_t_key,cma_t_address *_value); /* * Operations for alerts. */ /* * The current thread can request that a thread terminate it's execution. */ extern void cma_thread_alert (cma_t_thread *); /* * The current thread can poll for alert delivery. */ extern void cma_alert_test (void); /* * The current thread can disable asynchronous alert delivery, restore the * previous state of asynchronous alert delivery, or enable asynchronous * alert delivery. */ extern void cma_alert_disable_asynch (cma_t_alert_state *); extern void cma_alert_disable_general (cma_t_alert_state *); extern void cma_alert_enable_asynch (void); extern void cma_alert_enable_general (cma_t_alert_state *); extern void cma_alert_restore (cma_t_alert_state *); /* * Operations on stacks */ typedef cma_t_handle cma_t_stack_np; typedef void (*cma_t_call_routine) (void); /* * Allocate stack space */ extern void cma_stack_allocate_np (cma_t_integer,cma_t_address *); /* * Assign a stack to a thread */ extern void cma_stack_assign_np (cma_t_stack_np *,cma_t_thread *); /* * Call a routine on a new stack */ extern void cma_stack_call_routine_np (cma_t_stack_np *,cma_t_call_routine,cma_t_address,cma_t_address *); /* * Check stack limit */ extern cma_t_boolean cma_stack_check_limit_np (cma_t_integer); /* * Create a new stack */ extern void cma_stack_create_np (cma_t_stack_np *,cma_t_attr *); /* * Delete a stack */ extern void cma_stack_delete_np (cma_t_stack_np *); /* * Debug threads */ extern void cma_debug (void); extern void cma_debug_cmd (char *, ...); #ifndef _CMA_SUPPRESS_EXTERNALS_ _CMA_IMPORT_ void (*cma_g_debug) (void); #endif #ifdef __cplusplus } #endif # if defined(_HP_LIBC_R) && defined(__hpux1010p) # define sigaction _sigaction_sys # endif # if _CMA_OS_ == _CMA__VMS # include <cma_px.h> # else# include <dce/cma_px.h> # endif #if _CMA_UNIPROCESSOR_ # if _CMA_OS_ == _CMA__VMS # include <cmalib_crtlx.h> # else# include <dce/cmalib_crtlx.h> # endif#endif # ifndef _CMA_NOWRAPPERS_ # if !_CMA_REENTRANT_CLIB_ # if _CMA_OS_ == _CMA__VMS # include <cmalib_crtlx.h> # else# include <dce/cma_errno.h> # include <dce/cmalib_crtlx.h> # include <dce/cma_stdio.h> # endif# elif (_CMA_UNIX_TYPE == _CMA__SVR4) /* * SVR4 reentrant libraries do not have per-thread errno. */ # include <dce/cma_errno.h> # endif# if _CMA_OS_ == _CMA__UNIX # include <dce/cma_ux.h> # endif# if _CMA_OS_ == _CMA__VMS # include <cma_sigwait.h> # else# include <dce/cma_sigwait.h> # endif# endif # ifdef _HP_LIBC_R # undef wait # include <cma_libc_calls.h> # endif #endif </"dce/cma.h> ----------------------------------------------------------------------- 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

boost python error catching
by cseymour＠interchange.ubc.ca 15 Aug '02

15 Aug '02

Hi, I have some code that worked fine with Python 2.1, but now in Python 2.2.1 it segfaults mysteriuosly. I've narrowed it down to weirdness with the throw/catch of errors. When I do a throw "boost::python::error_already_set();", the "catch(...)" in my module cpp file is supposed to catch it. But it never gets to there. After it's thrown, Python just segfaults and dies. In Python 2.1 it worked perfectly but not in 2.2.1. Any suggestions?

1 0

Boost 1.28 and compile failure in use_count_is_zero class
by david_at_2good 15 Aug '02

15 Aug '02

I am using the free C++Builder Compiler version 5.5.1 for Win32. (http://www.borland.com/products/downloads/download_cbuilder.html) I have used Boost 1.27 without problems, but when compiling the same code with Boost 1.28 I get this error message for the compiler: Error E2113 c:\borland\boost_1_28_0\boost/detail/shared_count.hpp 39: Virtual function 'use_count_is_zero::what() const throw()' conflicts with base class 'exception' The class use_count_is_zero (new in Boost 1.28) inherits from std::exception, and it seems like the method prototype for what() is different in the Borland include files and Boost. Boost: class use_count_is_zero: public std::exception { public: virtual char const * what() const throw() { return "use_count_is_zero"; } }; Borland, who seem to use STL from Rogue Wave Software: class _RWSTDExport exception { public: exception () _RWSTD_THROW_SPEC_NULL { ; } exception (const exception&) _RWSTD_THROW_SPEC_NULL { ; } #if defined(_MSC_VER) && !defined(__BORLANDC__) exception (const char *s) _RWSTD_THROW_SPEC_NULL { ; } #endif exception& operator= (const exception& e) _RWSTD_THROW_SPEC_NULL { return *this; } virtual ~exception () _RWSTD_THROW_SPEC_NULL; virtual const char * what () const _RWSTD_THROW_SPEC_NULL { return __RWSTD::__rw_stdexcept_NoNamedException; } }; The content of _RWSTD_THROW_SPEC_NULL is set in the file stdcomp.h, and it seems like it is empty for the Borland compiler, so I tried to copy the declaration from Borland like below, but got the same error. class use_count_is_zero: public std::exception { public: virtual const char * what () const _RWSTD_THROW_SPEC_NULL { return "use_count_is_zero"; } }; Any suggestions? \David

2 4

boost.bind and g++ 2.95.3 woes
by yg-boost-users＠m.gmane.org 15 Aug '02

15 Aug '02

Hi there, I have a problem compiling the following code with g++ 2.95.3 and boost 1.28.0. ---%<--- #include <boost/bind.hpp> #include <boost/function/function0.hpp> struct A { A(boost::function0<void> const &) { } }; void foo(boost::function0<void> const &) {} void bar(unsigned int) {} int main(int argc, char *argv[]) { boost::bind(foo, boost::bind(bar, 0)); // ok A a1(boost::bind(bar, 0)); // ok A a2(boost::bind(foo, boost::bind(bar, 0))); // error return 0; } --->%--- The line marked with error gives me a whole flood of error messages. Is this a problem with my version of gcc? Or am I doing a stupid mistake? TIA, Markus PS: Here are the errors I get: /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp: In method `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::function0<void>(void)': /opt/ginit/lib/boost-1.28.0/boost/bind.hpp:163: instantiated from `boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > >::operator ()<void, void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &), boost::_bi::list0>(boost::_bi::type<void>, void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &), boost::_bi::list0 &) const' /opt/ginit/lib/boost-1.28.0/boost/bind/bind_template.hpp:21: instantiated from `boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >::operator ()()' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:127: instantiated from `boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >,void>::invoke(boost::detail::function::any_pointer)' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:437: instantiated from `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::assign_to<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > > >(boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >, boost::detail::function::function_obj_tag)' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:388: instantiated from `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::assign_to<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > > >(boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >)' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:274: instantiated from `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::function0<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > > >(boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >)' test_bind.cpp:16: instantiated from here /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:271: parameter `f' declared void /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:274: `f' undeclared (first use this function) /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:274: (Each undeclared identifier is reported only once /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:274: for each function it appears in.) /opt/ginit/lib/boost-1.28.0/boost/bind.hpp: In method `void boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > >::operator ()<void, void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &), boost::_bi::list0>(boost::_bi::type<void>, void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &), boost::_bi::list0 &) const': /opt/ginit/lib/boost-1.28.0/boost/bind/bind_template.hpp:21: instantiated from `boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >::operator ()()' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:127: instantiated from `boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >,void>::invoke(boost::detail::function::any_pointer)' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:437: instantiated from `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::assign_to<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > > >(boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >, boost::detail::function::function_obj_tag)' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:388: instantiated from `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::assign_to<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > > >(boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >)' /opt/ginit/lib/boost-1.28.0/boost/function/function_template.hpp:274: instantiated from `boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int>::function0<boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > > >(boost::_bi::bind_t<void,void (*)(const boost::function0<void,boost::empty_function_policy,boost::empty_function_mixin,int> &),boost::_bi::list1<boost::_bi::bind_t<void,void (*)(unsigned int),boost::_bi::list1<boost::_bi::value<int> > > > >)' test_bind.cpp:16: instantiated from here /opt/ginit/lib/boost-1.28.0/boost/bind.hpp:163: Internal compiler error in `emit_move_insn_1', at expr.c:2829 Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

3 2

gcc 2.95.3 vs gcc 3.1.1 vs intel c++ 6.0 with BGL and MTL
by Wintermantel , Marc 15 Aug '02

15 Aug '02

Hi, We are working on a Finite Element Library (FELyX - http://felyx.sourceforge.net <http://felyx.sourceforge.net/> ) that makes intensive use of the Boost Graph Library (BGL) as well as the Matrix Template Library (MTL). Up to now we worked with gcc 2.95.3 on Linux (AMD XP2000+ and P4 2.2GHz). Due to several sources on the internet we heard, that gcc 3.1.1 should be at least as fast as gcc 2.95.3 and the Intel c++ 6.0 should be even quite a bit faster then the other two. We used with all three of them -O3 Optimization, but our results up to now are rather disappointing. For a typical calculation we received the following results: Gcc 2.95.3 3.5 sec Gcc 3.1.1 3.9 sec Intel C++ 6.0 8.2 sec The results were quasi identical on both machines. We also tried a Intel PIII 850MHz in a notebook, and the times just scaled up. Further we looked at BGL, MTL and our own code separately and it came out that every part of the code loses almost equally compared to 2.95.3. Has anybody similar experiences or a hint what we could do wrong? Yours truly, Marc Wintermantel Marc Wintermantel IMES - Structures Technology ETH Zurich, LEO C4 Leonhardstrasse 27 CH- 8092 Zurich Tel. ++41 1 633 35 32 Fax. ++41 1 632 17 02 [Non-text portions of this message have been removed]

1 0

re: python weirdness
by cseymour＠interchange.ubc.ca 14 Aug '02

14 Aug '02

hi, i fixed that problem, by using linux_gcc.mak instead of gcc.mak, though now i'm back to where i was with older Boost, where i'm getting seg faults instead of Python errors. (btw linux_gcc.mak is kind of off: the suggested path for the BOOST macro is incorrect, and where $(BOOST) is used I found actually $(ROOT) should be used)

1 0

boost python weirdness - python2.2.1
by cseymour＠interchange.ubc.ca 14 Aug '02

14 Aug '02

hi, I had this extension module for python working fine with older versions of Boost and Python 2.1 but now we've updated to gcc 3 and Python 2.2 and it crashes weirdly, so I decided to try the latest version of Boost. I built the boost python library using /libs/python/build/gcc.mak. Everything seems okay, but when I try to load my library in Python I get: ImportError: ./HDF.so: undefined symbol: do_call__CQ45boost6python6detail4initP7_objectT1 when I check the symbols in my library I have this: U do_call__CQ45boost6python6detail4initP7_objectT1 and a whole lot of things like this: 00199d70 W do_call__CQ45boost6python6detailt24wrapped_function_pointer2ZQ23hdf11HDFVariableZPMQ23hdf7HDFFileFPQ23hdf7HDFFileRCQ35boost6python6stringcRCQ35boost6python5tuple_Q23hdf11HDFVariableP7_objectT1

1 0

graph: edge cuts
by Matthew Galati 14 Aug '02

14 Aug '02

is this a place for simple usage questions? i am a newbie... i want to use graph to return the set of edges in a cut for an undirected graph... that is, for some subset W of N, i want all e = {i in N, j in N} in E such that i is in W and j is not in W is there something built into graph to do this? or should i just do it manually from the adjacency list? thanks, matt -- Matthew Galati Lehigh University, Bethlehem, PA - Operations Research, M.S. Stetson University, Deland, FL - Mathematics, B.S. Office Phone: 610-758-4042 Email: magh(a)lehigh.edu URL: http://www.lehigh.edu/~magh/magh.html

2 1

adge properties getting corrupted when removing edge
by Jakub Plichta 13 Aug '02

13 Aug '02

Hello I have encountered the following problem and so far I have not been able to find a workaround. I start with a bidirectional graph with 4 nodes A, B, C and D. There is a integer edge property installed and I have following edges and their respective properties: E1 = C->B; prop[E1] = 0 E2 = D->B; prop[E2] = 1 E3 = B->A; prop[E3] = 0 I am removing edge E3 and immediately after remove_edge the property for E1 is 1 which is wrong. Is this a known issue? I would really appreciate any suggestions. Thanks Jakub Plichta [Non-text portions of this message have been removed]

1 0