Re: python , Boost and straight (but complex) C code



Osiris wrote:

On Sat, 30 Dec 2006 13:19:28 -0800, Erik Max Francis <max@xxxxxxxxxxx>
wrote:

Osiris wrote:

I have these pieces of C-code (NOT C++ !!) I want to call from Python.
I found Boost.
I have MS Visual Studio 2005 with C++.

is this the idea:
I write the following C source file:
============================
#include <iostream>
#include <stdafx.h>

namespace { // Avoid cluttering the global namespace.

iostream and namespaces are both most definitely C++ features, not C.

yes, but C can be compiled with a C++ compiler, One can put C code in
C++ source.... Boost should not complain... should it ?
Boost text is all about C++.. so... C should not be a problem...

Not all C code can be compiled by a C++ compiler. And anyway, this is
definitively NOT C code.
.



Relevant Pages

  • Re: python , Boost and straight (but complex) C code
    ... I write the following C source file: ... namespace {// Avoid cluttering the global namespace. ... Boost should not complain... ... Not all C code can be compiled by a C++ compiler. ...
    (comp.lang.python)
  • Re: python , Boost and straight (but complex) C code
    ... namespace {// Avoid cluttering the global namespace. ... yes, but C can be compiled with a C++ compiler, One can put C code in ... Boost should not complain... ...
    (comp.lang.python)
  • Re: python , Boost and straight (but complex) C code
    ... I found Boost. ... I have MS Visual Studio 2005 with C++. ... I write the following C source file: ... namespace {// Avoid cluttering the global namespace. ...
    (comp.lang.python)
  • Very strange problem with namespace
    ... reference that is returned by an iterator. ... No matter what, the compiler ... contains item_proxy as an inner class) is not defined in namespace N, ... // without putting ContainerFront into namespace N ...
    (microsoft.public.vc.language)
  • Re: How to fix awkward ATL namespace clash?
    ... Renaming my own namespace doesn't work because I'm not getting a namespace ... I'm getting an Interface collision. ... By the time the compiler parses my typelib the OLEDB IAccessor ...
    (microsoft.public.vc.atl)