Mailman 3 June 2005 - Cplusplus-sig

CFP: IEEE inco-operated International Conference on Computational Intelligence for Modelling, Control and Automation
by cimca June 18, 2005

June 18, 2005

CALL FOR PAPERS International Conference on Computational Intelligence for Modelling, Control and Automation 28 - 30 November 2005 Vienna, Austria http://www.ise.canberra.edu.au/conferences/cimca05/ In co-operation with: IEEE Computational Intelligence Society Conference Proceedings will be published as books by IEEE (The Institute of Electrical and Electronic Engineering) Sponsored by: European Society for Fuzzy Logic and Technology - EUFLAT International Association for Fuzzy Set in Management and Economy - SIGEF Japan Society for Fuzzy Theory and Intelligent Informatics - SOFT Taiwan Fuzzy Systems Association - TFSA World Wide Web Business Intelligence - W3BI Hungarian Fuzzy Association - HFA University of Canberra Jointly with International Conference on Intelligent Agents, Web Technologies and Internet Commerce http://www.ise.canberra.edu.au/conferences/iawtic05/ Honorary Chair: Lotfi A. Zadeh, University of California, USA Stephen Grossberg, Boston University, USA The international conference on computational intelligence for modelling, control and automation will be held in Vienna, Austria on 28 to 30 November 2005. The conference provides a medium for the exchange of ideas between theoreticians and practitioners to address the important issues in computational intelligence, modelling, control and automation. The conference will consist of both plenary sessions and contributory sessions, focusing on theory, implementation and applications of computational intelligence techniques to modelling, control and automation. For contributory sessions, papers (4 pages or more) are being solicited. Several well-known keynote speakers will address the conference. Conference Proceedings will be published as books by IEEE (The Institute of Electrical and Electronic Engineering) in USA and will be index world wide. All papers will be peer reviewed by at least two reviewers. Topics of the conference include, but are not limited to, the following areas: Modern and Advanced Control Strategies: Neural Networks Control, Fuzzy Logic Control, Genetic Algorithms and Evolutionary Control, Model-Predictive Control, Adaptive and Optimal Control, Intelligent Control Systems, Robotics and Automation, Fault Diagnosis, Intelligent agents, Industrial Automations Hybrid Systems: Fuzzy Evolutionary Systems, Fuzzy Expert Systems, Fuzzy Neural Systems, Neural Genetic Systems, Neural-Fuzzy-Genetic Systems, Hybrid Systems for Optimisation Data Analysis, Prediction and Model Identification: Signal Processing, Prediction and Time Series Analysis, System Identification, Data Fusion and Mining, Knowledge Discovery, Intelligent Information Systems, Image Processing, and Image Understanding, Parallel Computing applications in Identification & Control, Pattern Recognition, Clustering and Classification Decision Making and Information Retrieval: Case-Based Reasoning, Decision Analysis, Intelligent Databases & Information Retrieval, Dynamic Systems Modelling, Decision Support Systems, Multi-criteria Decision Making, Qualitative and Approximate-Reasoning Paper Submission Papers will be selected based on their originality, significance, correctness, and clarity of presentation. Papers (4 pages or more) should be submitted to the following e-mail or the following address: CIMCA'2005 Secretariat School of Information Sciences and Engineering University of Canberra, Canberra, 2616, ACT, Australia E-mail: cimca(a)canberra.edu.au Electronic submission of papers (either by E-mail or through conference website) is preferred. Draft papers should present original work, which has not been published or being reviewed for other conferences. Important Dates 31 August 2005 Submission of draft papers 30 September 2005 Notification of acceptance 21 October 2005 Deadline for camera-ready copies of accepted papers 28-30 November 2005 Conference sessions Special Sessions and Tutorials Special sessions and tutorials will be organised at the conference. The conference is calling for special sessions and tutorial proposals. All special session proposals should be sent to the conference chair (by email to: masoud.mohammadian(a)canberra.edu.au) on or before 5th of August 2005. CIMCA'05 will also include a special poster session devoted to recent work and work-in-progress. Abstracts are solicited for this session. Abstracts (3 pages limit) may be submitted up to 30 days before the conference date. Visits and social events Sightseeing visits will be arranged for the delegates and guests. A separate program will be arranged for companions during the conference. Further Information For further information either contact cimca(a)ise.canberra.edu.au or see the conference homepage at: http://www.ise.canberra.edu.au/conferences/cimca05/default.htm Organising Committee Chair: Masoud Mohammadian, University of Canberra, Australia International Program Committee: H. Adeli, The Ohio State University, USA W. Pedrycz, University of Manitoba, Canada A. Agah, The University of Kansas, USA T. Fukuda, Nagoya University, Japan J. Bezdek, University of West Florida, USA R. C. Eberhart, Purdue University, USA F. Herrera, University of Granada, Spain T. Furuhashi, Nagoya University, Japan A. Agah, The University of Kansas, US E. André, Universität Augsburg, Germany A. Kandel, University of South Florida, USA J. P. Bigus, IBM T. J. Watson Research Center, USA J. Liu, Hong Kong Baptist University, Hong Kong A. Namatame, National Defense Academy, Japan K. Sycara, Carnegie Mellon University, USA B. Kosko, University of Southern California, USA T. Baeck, Informatic Centrum Dortmund, Germany K. Hirota, Tokyo Institute of Technology, Japan E. Oja, Helsinki University of Technology, Finland H. R. Berenji, NASA Ames Research Center, USA H. Liljenstrom, Royal Institute of Technology, Sweden A. Bulsari, AB Nonlinear Solutions OY, Finland J. Fernandez de Cañete, University of Malaga, Spain W. Duch, Nicholas Copernicus University, Poland E. Tulunay, Middle East Technical University, Turkey C. Kuroda, Tokyo Institute of Technology, Japan T. Yamakawa, Kyushu Institute of Technology, Japan J. Liu, Hong Kong Baptist University, Hong Kong A. Namatame, National Defense Academy, Japan A. Aamodt, Norwegian University of Science & Technology, Norway International Liaison: Canada and USA Liaison: Robert John, De Montfort University, UK Nasser Jazdi, Institut für Automatisierungs- und Softwaretechnik, Germany Europe Liaison: Dr. Eng. Djamel Khadraoui, Centre de Recherche Public, Luxembourg Frank Zimmer, SES ASTRA, Luxembourg Asia Liaison: Renzo Gobbin, University of Canberra, Australia R. Amin Sarker, ADFA, Australia Local Arrangements and Public Relation: Zohreh Pahlavani, AVIP, Austria C Meier, Australia Publicity: C. Meier, Australia Zohreh Pahlavani, AVIP, Austria Publication: Masoud Mohammadian, Australia In cooperation with: University of Canberra, (Masoud Mohammadian) Universidad Carlos III de Madrid, (José-Luis Fernández-Villacañas Martín) University of Guelph, (Simon X. Yang)

1 0

solaris: import module error
by Atul Kshirsagar June 16, 2005

June 16, 2005

Hello, I am embedding python in C++ using SWIG. * The appication runs as a server. * Mutiple clients send requests which execute some python scripts with import statements. * Each request is handled in a separate thread which has its own interepreter for script execution. * Requests are succesfully completed fine for some time and then I see some "ImportErrors" for example "ImportError: No module named string" Apart from these python replated errors I see some "too many files open" errors in my other server code. Other than solaris things work fine on other unix platforms and windos too. One additional thing I do for solaris is "import DLFCN; sys.setdlopenflags(DLFCN.RTLD_NOW | DLFCN.RTLD_PARENT);" One of my question is, is importing some module create a file handle ? Any help on this is appreciated. Thanks, Atul Kshirsagar __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [C++-sig] Boost.Python
by David Abrahams June 16, 2005

June 16, 2005

Followups to the C++-sig, please. "Drumheller, Michael" <michael.drumheller(a)boeing.com> writes: > David: > > > a really great facility, and I am excited to try it out. > > Thanks; that's always gratifying to hear! > > You're welcome! > > > I have a question though: In the Tutorial->Embedding section, > > http://www.boost.org/libs/python/doc/tutorial/doc/html/python/embedding.html > > it says "Currently, Boost.Python does not directly support everything > > you'll need when embedding." However, in other sections, such as the Ref Man page > > http://www.boost.org/libs/python/doc/v2/call_method.html, it seems to suggest > > that there is very powerful support for calling Python functions/methods etc. > > from C++. > > > > Are these documents just out of sync, or am I misunderstanding > > something? > > I guess the latter. Despite that powerful support you mention, there > are still gaps in Boost.Python's wrapping of the Python/C API as you > can see from the example. > > OK, thank you. I think this is rather a serious doc bug. The smallest mistakes can look serious if they lead you down the wrong path. > I very nearly dismissed Boost.Python summarily as useless (to me) > upon reading the Tutorial section. (This is because my initial > interest is in calling Python from C++, not building C++ > extensions.) If you don't mind me going into a little detail, I'd > like to explain how the documentation appeared to me, in particular > the browsing sequence that it "led me through": > > I started browsing the Boost.Python doc pages, and found at this > link pretty quickly: > http://www.boost.org/libs/python/doc/tutorial/doc/html/python/embedding.html. > (I found it because I first went to > http://www.boost.org/libs/python/doc/, and there I saw the tutorial > link > http://www.boost.org/libs/python/doc/tutorial/doc/html/index.html. > A tutorial is *always* the first thing I look for, so I went there.) > I saw the "Embedding" item in the contents. Clicking there, I saw > right at the top of the first page the statement "...sometimes you > may need to do the reverse: call Python code from the C++-side." So > I thought "A-ha, this is what I was looking for. I am definitely in > the right place." > > But when I read the rest of that page, all I saw stuff for eval'ing > a string or file. So I thought, "Hmmm, this stuff has not gone very > far beyond what Python has been able to do forever." If you can make some _specific_ suggestions about how to reformulate that page, they'd be greatly appreciated. I mean, "add this text here, delete that text, stick a link here to whatever." > I can't recall how I found the other link > http://www.boost.org/libs/python/doc/v2/call_method.html, but it > definitely took more time and resourcefulness on my part than it > should have. That might be good, because you shouldn't use it ;-). The object interface described at http://www.boost.org/libs/python/doc/tutorial/doc/html/python/object.html is much cleaner and generally more effective. > I think Boost (and maybe Boost Consulting!) might be losing a > potential user/customer now and then because of this--that is, > because of the failure of the "Embedding" section to point to all > the cool "callable" stuff. Well, yeah, I agree we could do better. That said, if a person is going to dive into the middle of the documentation, they're going to miss some things. You can only point to so many cool things from any page before the whole doc becomes terribly redundant. > To view it in the worst possible light, it is rather a glaring > inadequacy, and such inadequacies, as you know, tend to cause doubts > in people's minds as to the professional quality of a piece of > software, and, speaking for myself, it tends to make one wonder > whethere anyone is using, maintaining, or even paying attention to > it. (In fact, given that Boost has been around for a while, I find > it kind of puzzling that I should be the first person to notice this > particular problem.) It's getting plenty of use and -- at the moment -- not as much maintenance attention as I'd like. Boost.Python is at its healthiest when someone is funding development, but I do try to stay on top of the critical things all the time. > Another suggestion, while I'm at it, is this: I think the > Boost.Python html docs *definitely* need to be supplemented with > either/or/both (a) a one-page html version, (b) a pdf version. The > reason is to provide easy searchability. If the Boost.Python docs > were searchable, I might have found what I was looking for faster. I can easily put a "search Boost.Python docs" box on the library's front page without changing the format. That's a good idea. In the meantime, try typing your search terms into Google, followed by site:http://www.boost.org/libs/python/doc > All that being said, I'd like to say again that I am fascinated and impressed > by the capabilities described therein and I'm looking forward to trying it out! Thanks a lot! -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 3

Wrapping boost::multi_array
by Thomas Kolb June 16, 2005

June 16, 2005

Hi all, I have lots of classes in my library that deal heavily with boost::multi_array, so I'm trying to wrap this class for some special dimensions and data types. My source code is: namespace { typedef boost::multi_array<double, 1> DoubleVector; DoubleVector* cTorWrapper(unsigned int size) { return new DoubleVector(boost::extents[size]); } double& operatorWrapper(DoubleVector& vec, DoubleVector::size_type id) { return vec[0]; } }// namespace // Module ====================================================================== void Export_Multi_Array() { class_< DoubleVector, std::auto_ptr<DoubleVector> >("DoubleVector") .def("__init__", make_constructor(cTorWrapper)) .def("get",&operatorWrapper, return_internal_reference< 1 >()) ; } this leads to the following compiler error: /usr/local/include/boost-1_31/boost/python/object/make_instance.hpp: In static member function `static PyObject* boost::python::objects::make_instance_impl<T, Holder, Derived>::execute(Arg&) [with Arg = double*, T = double, Holder = boost::python::objects::pointer_holder<double*, double>, Derived = boost::python::objects::make_ptr_instance<double, boost::python::objects::pointer_holder<double*, double> >]': /usr/local/include/boost-1_31/boost/python/to_python_indirect.hpp:64: instantiated from `static PyObject* boost::python::detail::make_reference_holder::execute(T*) [with T = double]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:19: instantiated from `typename Generator::result_type boost::python::detail::unwind_type_cv(U*, boost::python::detail::cv_tag<false, false>, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = double]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:48: instantiated from `typename Generator::result_type boost::python::detail::unwind_ptr_type(U*, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = double]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:58: instantiated from `static typename Generator::result_type boost::python::detail::unwind_helper<is_ptr>::execute(U, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = double*, bool is_ptr = true]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:77: instantiated from `typename Generator::result_type boost::python::detail::unwind_type(const U&, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = double*]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:26: instantiated from `typename Generator::result_type boost::python::detail::unwind_type_cv(const U*, boost::python::detail::cv_tag<true, false>, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = double]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:48: instantiated from `typename Generator::result_type boost::python::detail::unwind_ptr_type(U*, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = const double]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:69: instantiated from `static typename Generator::result_type boost::python::detail::unwind_helper<false>::execute(U&, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = const double]' /usr/local/include/boost-1_31/boost/python/detail/unwind_type.hpp:77: instantiated from `typename Generator::result_type boost::python::detail::unwind_type(const U&, Generator*) [with Generator = boost::python::detail::make_reference_holder, U = double]' /usr/local/include/boost-1_31/boost/python/to_python_indirect.hpp:105: instantiated from `PyObject* boost::python::to_python_indirect<T, MakeHolder>::operator()(T) const [with T = double&, MakeHolder = boost::python::detail::make_reference_holder]' /usr/local/include/boost-1_31/boost/python/detail/invoke.hpp:76: instantiated from `PyObject* boost::python::detail::invoke(boost::python::detail::invoke_tag_<false, false>, const RC&, F&, AC0&, AC1&) [with RC = boost::python::to_python_indirect<double&, boost::python::detail::make_reference_holder>, F = double&(*)(<unnamed>::DoubleVector*, long unsigned int), AC0 = boost::python::arg_from_python<<unnamed>::DoubleVector*>, AC1 = boost::python::arg_from_python<long unsigned int>]' /usr/local/include/boost-1_31/boost/python/detail/caller.hpp:199: instantiated from `PyObject* boost::python::detail::caller_arity<2>::impl<F, Policies, Sig>::operator()(PyObject*, PyObject*) [with F = double&(*)(<unnamed>::DoubleVector*, long unsigned int), Policies = boost::python::return_internal_reference<1, boost::python::default_call_policies>, Sig = boost::mpl::vector3<double&, <unnamed>::DoubleVector*, long unsigned int>]' /usr/local/include/boost-1_31/boost/python/object/py_function.hpp:39: instantiated from `PyObject* boost::python::objects::caller_py_function_impl<Caller>::operator()(PyObject*, PyObject*) [with Caller = boost::python::detail::caller<double&(*)(<unnamed>::DoubleVector*, long unsigned int), boost::python::return_internal_reference<1, boost::python::default_call_policies>, boost::mpl::vector3<double&, <unnamed>::DoubleVector*, long unsigned int> >]' /usr/local/include/boost-1_31/boost/python/make_constructor.hpp:40: instantiated from here /usr/local/include/boost-1_31/boost/python/object/make_instance.hpp:25: error: invalid application of `sizeof' to an incomplete type returning the result of operator[] by values compiles great, but that's not what I want. Anybody has an idea what's wrong? Best Regards

2 2

Creating an instance of a Python class
by Antony Trupe June 15, 2005

June 15, 2005

I need to instantiate a class defined in python code in c/c++ code, and call its methods. Any advice or directions to advice would be appreciated.

1 0

Re: [C++-sig] examples compile but give exception (win32; intel 8.1; dinkumware 3.08)
by Jens B. Jorgensen June 15, 2005

June 15, 2005

> -----Original Message----- > From: c++-sig-bounces(a)python.org [mailto:c++-sig-bounces@python.org]On > Behalf Of David Abrahams > Sent: Tuesday, June 14, 2005 12:59 PM > To: c++-sig(a)python.org > Subject: Re: [C++-sig] examples compile but give exception > (win32; intel > 8.1;dinkumware 3.08) > > > "Jens B. Jorgensen" <jorgensen(a)getcollc.com> writes: > > > Sorry, the below makes me look like an idiot (I'm not > asserting I'm not, but what you see below is actually not > what I intended). Clearly the hello constructor in > getting_started2 requires an argument. I first saw the error > below in a different piece of code (one I wrote) and I > quickly tried the example to verify that I was getting the > same thing. In any case, writing proper Python I get: > > > > Python 2.4.1 (#65, Mar 30 2005, 09:13:57) [MSC v.1310 32 > bit (Intel)] on win32 > > Type "help", "copyright", "credits" or "license" for more > information. > >>>> import getting_started2 > >>>> h = getting_started2.hello('hello, world') > > Traceback (most recent call last): > > File "<stdin>", line 1, in ? > > Boost.Python.ArgumentError: Python argument types in > > hello.__init__(hello, str) > > did not match C++ signature: > > __init__(struct _object *, class > std::basic_string<char,struct std::char_tra > > its<char>,class std::allocator<char> >) > >>>> > > Looks like a problem with RTTI. Did you perhaps have it turned off in > your extension module? Nope, definitely left that on. I guess I'll have to debug into the code. Any pointers on the best place to start looking for that? It's a little confusing since everything is declarative. Is the error triggered by an exception? A cast that fails? How does it work? > Incidentally, I think you went about making the toolset the hard way. > Seems like using a rather big hammer to be manually injecting the > compiler flags; you might easily be countermanding something that the > build system is doing on purpose in order to make Boost.Python work on > intel-windows. > > I would take intel-win32-stlport-tools.jam as my model if I were you. That's pretty much what I did, although I started with intel-win32-tools.jam. Rest assured I didn't generate it from scratch. The main thing I started from was that I needed to link to the Dinkumware stdlib and then dealt with all the stuff that broke. One thing that I haven't quite figured out yet: I see postings here and there referring to tests that can be built and run but I haven't yet figured out how to get them built. Is there actually any documentation around that indicates how this is to be done? Thanks again for any suggestions or pointers.

2 1

Re: [C++-sig] examples compile but give exception (win32; intel 8.1; dinkumware 3.08)
by Jens B. Jorgensen June 14, 2005

June 14, 2005

Sorry, the below makes me look like an idiot (I'm not asserting I'm not, but what you see below is actually not what I intended). Clearly the hello constructor in getting_started2 requires an argument. I first saw the error below in a different piece of code (one I wrote) and I quickly tried the example to verify that I was getting the same thing. In any case, writing proper Python I get: Python 2.4.1 (#65, Mar 30 2005, 09:13:57) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import getting_started2 >>> h = getting_started2.hello('hello, world') Traceback (most recent call last): File "<stdin>", line 1, in ? Boost.Python.ArgumentError: Python argument types in hello.__init__(hello, str) did not match C++ signature: __init__(struct _object *, class std::basic_string<char,struct std::char_tra its<char>,class std::allocator<char> >) >>> Or running the test_getting_started2.py I get: ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 2, in test_getting_started2 Failed example: hi = hello('California') Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[1]>", line 1, in ? hi = hello('California') ArgumentError: Python argument types in hello.__init__(hello, str) did not match C++ signature: __init__(struct _object *, class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >) ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 3, in test_getting_started2 Failed example: hi.greet() Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[2]>", line 1, in ? hi.greet() NameError: name 'hi' is not defined ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 5, in test_getting_started2 Failed example: invite(hi) Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[3]>", line 1, in ? invite(hi) NameError: name 'hi' is not defined ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 7, in test_getting_started2 Failed example: hi.invite() Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[4]>", line 1, in ? hi.invite() NameError: name 'hi' is not defined ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 14, in test_getting_started2 Failed example: hi2 = wordy('Florida') Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[6]>", line 1, in ? hi2 = wordy('Florida') ArgumentError: Python argument types in hello.__init__(wordy, str) did not match C++ signature: __init__(struct _object *, class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >) ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 15, in test_getting_started2 Failed example: hi2.greet() Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[7]>", line 1, in ? hi2.greet() NameError: name 'hi2' is not defined ********************************************************************** File "c:\boost_1_32_0\libs\python\example\test_getting_started2.py", line 17, in test_getting_started2 Failed example: invite(hi2) Exception raised: Traceback (most recent call last): File "C:\Python24\Lib\doctest.py", line 1243, in __run compileflags, 1) in test.globs File "<doctest test_getting_started2[8]>", line 1, in ? invite(hi2) NameError: name 'hi2' is not defined ********************************************************************** 1 items had failures: 7 of 9 in test_getting_started2 ***Test Failed*** 7 failures. > -----Original Message----- > From: c++-sig-bounces(a)python.org [mailto:c++-sig-bounces@python.org]On > Behalf Of Jens B. Jorgensen > Sent: Tuesday, June 14, 2005 8:42 AM > To: c++-sig(a)python.org > Subject: [C++-sig] examples compile but give exception (win32; intel > 8.1;dinkumware 3.08) > > > I have a problem that hopefully someone can give me some > insight to. I recently got Boost 1.32.0 to compile for my > environment. I'm using the Intel c++ compiler 8.1 and the > dinkumware std library v3.08. Getting everything to compile > ultimately required my own custom intel-win32-sxl-tools.jam > which I based on the intel-win32-tools.jam. The main options > I added to get that working are: > > CFLAGS += -I\"<path to dinkumware stdlib>" ; > CFLAGS += /D_GLOBAL_USING=1 /DBOOST_DATE_TIME_NO_LOCALE > /D_HAS_EXCEPTIONS=1 > /DBOOST_ARCHIVE_OLD_DINKUMWARE_BENEATH_STLPORT > -DBOOST_NO_EXCEPTION_STD_NAMESPACE /DBOOST_NO_STD_ALLOCATOR > -DBOOST_NO_STD_USE_FACET -DBOOST_HAS_TWO_ARG_USE_FACET ; > > e.g. if I use bjam "-sTOOLS=intel-win32-sxl" -n I see: > > CALL "c:\Program > Files\Intel\CPP\Compiler80\Ia32\bin\ICLVARS.BAT" > nul > "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\icl" > /Zm800 -nologo /EHsc -c -DBOOST_PYTHON_DYNAMIC_LIB /Z7 /Od > /Ob0 /EHsc /GR /MDd -I"C:\VendorAPIs\SXL\include" > /D_GLOBAL_USING=1 /DBOOST_DATE_TIME_NO_LOCALE > /D_HAS_EXCEPTIONS=1 > /DBOOST_ARCHIVE_OLD_DINKUMWARE_BENEATH_STLPORT > -DBOOST_NO_EXCEPTION_STD_NAMESPACE /DBOOST_NO_STD_ALLOCATOR > -DBOOST_NO_STD_USE_FACET -DBOOST_HAS_TWO_ARG_USE_FACET /Qwn5 > /Qwd985 -Qoption,c,--arg_dep_lookup /Zc:forScope /Qansi_alias > /Qvc6 -DBOOST_NO_INTRINSIC_WCHAR_T /EHa -I"bin\example" > -I"C:\Program Files\Microsoft Visual > Studio\VC98\include" -I"c:\boost_1_32_0" > -I"c:\Python24\include" > -Fo"bin\example\getting_started2.pyd\intel-win32-sxl\debug\thr > eading-multi\getting_started2.obj" > -Tp"c:\boost_1_32_0\libs\python\example\getting_started2.cpp" > > I arrived at my custom .jam through time patiently spent > looking at compiler error messages and the source. With the > above everything builds! Huzzah. We're using the Intel > compiler in an msvc6 "environment" at the moment so I've got /Qvc6. > > So, then I proceeded to the hello example that defines a > module with a "greet" function. Works fine. Then I tried to > get a little fancier and create an object. This builds but I > get a runtime error. So, ultimately I try using bjam to build > the example code included. Everything builds fine but when I > try to using the resulting python module I get some > interesting things: > > Python 2.4.1 (#65, Mar 30 2005, 09:13:57) [MSC v.1310 32 bit > (Intel)] on win32 > Type "help", "copyright", "credits" or "license" for more information. > >>> import getting_started2 > >>> h = getting_started2.hello() > Traceback (most recent call last): > File "<stdin>", line 1, in ? > Boost.Python.ArgumentError: Python argument types in > hello.__init__(hello) > did not match C++ signature: > __init__(struct _object *, class > std::basic_string<char,struct std::char_traits<char>,class > std::allocator<char> >) > > Any ideas? I've been pondering the lists but I'm stumped. > It's clear that someout it isn't able to map the class but I > have no idea why. The above module was compiled from the > source included in the distribution, I made no changes to the source. > > Thanks for any help or pointers, > > Jens B. Jorgensen > Getco, LLC > > > _______________________________________________ > C++-sig mailing list > C++-sig(a)python.org > http://mail.python.org/mailman/listinfo/c++-sig >

2 1

Any work for cyclic garbage collection support ?
by Pierre Barbier de Reuille June 14, 2005

June 14, 2005

Hello, I had the problem some years ago and did not succeed in using the cyclic garbage collector of Python with BPL objects. Now, I read a little more about it and I wonder if it is possible to add such support without many changes in BPL ! The fact is, the allocation is different, you have to initialise the structure of the class in the right way and you have to define some "traversal" function being able to enumerate all the objects potentially involve in some cycles. Is there any chance of this being supported ? Or at least, is there a way to add the needed functions "by hands" ? Hope I was clear enough, Pierre -- Pierre Barbier de Reuille INRA - UMR Cirad/Inra/Cnrs/Univ.MontpellierII AMAP Botanique et Bio-informatique de l'Architecture des Plantes TA40/PSII, Boulevard de la Lironde 34398 MONTPELLIER CEDEX 5, France tel : (33) 4 67 61 65 77 fax : (33) 4 67 61 56 68

2 1

examples compile but give exception (win32; intel 8.1; dinkumware 3.08)
by Jens B. Jorgensen June 14, 2005

June 14, 2005

I have a problem that hopefully someone can give me some insight to. I recently got Boost 1.32.0 to compile for my environment. I'm using the Intel c++ compiler 8.1 and the dinkumware std library v3.08. Getting everything to compile ultimately required my own custom intel-win32-sxl-tools.jam which I based on the intel-win32-tools.jam. The main options I added to get that working are: CFLAGS += -I\"<path to dinkumware stdlib>" ; CFLAGS += /D_GLOBAL_USING=1 /DBOOST_DATE_TIME_NO_LOCALE /D_HAS_EXCEPTIONS=1 /DBOOST_ARCHIVE_OLD_DINKUMWARE_BENEATH_STLPORT -DBOOST_NO_EXCEPTION_STD_NAMESPACE /DBOOST_NO_STD_ALLOCATOR -DBOOST_NO_STD_USE_FACET -DBOOST_HAS_TWO_ARG_USE_FACET ; e.g. if I use bjam "-sTOOLS=intel-win32-sxl" -n I see: CALL "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\ICLVARS.BAT" > nul "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\icl" /Zm800 -nologo /EHsc -c -DBOOST_PYTHON_DYNAMIC_LIB /Z7 /Od /Ob0 /EHsc /GR /MDd -I"C:\VendorAPIs\SXL\include" /D_GLOBAL_USING=1 /DBOOST_DATE_TIME_NO_LOCALE /D_HAS_EXCEPTIONS=1 /DBOOST_ARCHIVE_OLD_DINKUMWARE_BENEATH_STLPORT -DBOOST_NO_EXCEPTION_STD_NAMESPACE /DBOOST_NO_STD_ALLOCATOR -DBOOST_NO_STD_USE_FACET -DBOOST_HAS_TWO_ARG_USE_FACET /Qwn5 /Qwd985 -Qoption,c,--arg_dep_lookup /Zc:forScope /Qansi_alias /Qvc6 -DBOOST_NO_INTRINSIC_WCHAR_T /EHa -I"bin\example" -I"C:\Program Files\Microsoft Visual Studio\VC98\include" -I"c:\boost_1_32_0" -I"c:\Python24\include" -Fo"bin\example\getting_started2.pyd\intel-win32-sxl\debug\threading-multi\getting_started2.obj" -Tp"c:\boost_1_32_0\libs\python\example\getting_started2.cpp" I arrived at my custom .jam through time patiently spent looking at compiler error messages and the source. With the above everything builds! Huzzah. We're using the Intel compiler in an msvc6 "environment" at the moment so I've got /Qvc6. So, then I proceeded to the hello example that defines a module with a "greet" function. Works fine. Then I tried to get a little fancier and create an object. This builds but I get a runtime error. So, ultimately I try using bjam to build the example code included. Everything builds fine but when I try to using the resulting python module I get some interesting things: Python 2.4.1 (#65, Mar 30 2005, 09:13:57) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import getting_started2 >>> h = getting_started2.hello() Traceback (most recent call last): File "<stdin>", line 1, in ? Boost.Python.ArgumentError: Python argument types in hello.__init__(hello) did not match C++ signature: __init__(struct _object *, class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >) Any ideas? I've been pondering the lists but I'm stumped. It's clear that someout it isn't able to map the class but I have no idea why. The above module was compiled from the source included in the distribution, I made no changes to the source. Thanks for any help or pointers, Jens B. Jorgensen Getco, LLC

1 0

Improved pyste
by Niall Douglas June 14, 2005

June 14, 2005

(The file is at http://www.nedprod.com/Pyste.zip as it seems you can't post attachments here) Enclosed is a further improved version of pyste over the one I sent some months ago. This is from the pyste in v1.32. Here are the changes: * Overloads were being declared multiply per code unit if they applied to each class, now they are output only once * friend functions of classes which overload weren't being distinguished between by casting (fixed by brute force casting all functions) * Outputs things missing a policy to a file for more easier browsing * Fixed a bug where it was missing "artificial" copy constructors ie; ones generated by the compiler * Got AllFromHeader() to maintain a list of things it exported so the pyste file can know what policies to apply. This is very much a hack and would conflict with anything in the header file called "exporter" * Fixed AllFromHeader() breaking application of bases<> to class definitions * Added new SplitOutput() directive which can split output into multiple files, thus avoiding MSVC's "internal structure overflow" error. Note that the implementation of this is pretty hacky This is in addition to the previous enhancements: * Support for void* by casting to void_* and treating it as an opaque pointer. This is a major new feature for wrapping most code. * Prevents the problem of throw() specifiers confusing Boost.Python by casting them off * Passing of gccxml errors out so you can see what's confusing GCC/GCCXML (handy when you develop primarily with MSVC) * Protected virtual methods are no longer wrapped as there were access problems. I've had similar problems with protected inheritance. Cheers, Niall

8 16