Boost logo

Boost :

From: rwgk_at_[hidden]
Date: 2000-12-15 11:16:50

I have copied the Python script to file
area for this egroup:

Running this script will create 17 cwhatever include files. E.g.:

// This file is automatically generated. Do not edit.
// ['/net/cci/rwgk/bin/']
// Fri Dec 15 07:43:45 2000 ('PST', 'PDT')


#include <wchar.h>

namespace std {
  using ::mbstate_t;
  using ::wint_t;
  using ::size_t;
#if !(defined(__sgi) && defined(_COMPILER_VERSION) &&
  using ::btowc;


I am not sure how well this fits in with John Maddock's ideas, but at
least makes the definitions from the ISO
standard more accessible (the information was copied directly from the
file ISO+IEC+14882-1998.pdf).

John Maddock wrote:
> simple wrappers that #include the name.h version, and #undef all
> prototypes (we must have real ANSI C prototypes and not macros, in
order to
> use the std::foo syntax). These files do not add the "using
> for the following reasons:

How exactly would this work?

Using the header files created by, the Boost
Python Library compiles with Compaq's Tru64 cxx compiler. The
comprehensive test checks out OK. The boost array.h also works in
my application.

The Boost Python Library also compiles with the native Silicon
compiler (MIPSpro However, when trying to import the shared
objects in Python, there is an unresovled symbol:

>>> import hello
Traceback (innermost last):
  File "<stdin>", line 1, in ?
ImportError: 30317:python: rld: Fatal Error: unresolvable symbol
in ./ _S_count__Q3_3std8ios_base4Init

Does this ring any bells?

It would be good to run the general boost regression tests, but I do
know what the setup is for this. Could someone please help?


Boost list run by bdawes at, gregod at, cpdaniel at, john at