[C++-SIG] RE: [META-SIG] Terminating comatose SIGs

[Paul F. Dubois]

Geoff's report that I have just gotten back to work on this is correct. I'm
going to want to get feedback on what I have done so far. Actually, the part
I'm working on at the moment doesn't even involve anything high-tech,
although I think eventually people are going to want the more elaborate
facilities. Here is a tiny example of the sort of thing I can do now, and am
going to want feedback on when I'm ready:

static Dict
test_dict() {
    // test the Dict class
    Dict a;
    a["hi"] = Stryng("ho");
    return a;
}

static PyObject*
ex_test (PyObject* self, PyObject* args)
{
    try {
        List a;
        Tuple t(args);
        for(Tuple::iterator i = t.begin(); i != t.end(); i++) {
            a.append(*i);
        }
        a.append(test_numbers());
        a.append(test_list());
        a.append(test_dict());
        return ort(a);
    }
    catch (const PyException&) {
        return Py_Null;
    }
}

So I would appreciate keeping this SIG alive until we've had more time to do
this work.

Or, as Jonathan Winters once remarked to a circling buzzard, "Hey, clown, I
ain't dead yet!".

-----Original Message-----
From: Phil Austin <phil at geog.ubc.ca>
To: Geoffrey M. Furnish <furnish at xdiv.lanl.gov>
Cc: Guido van Rossum <guido at CNRI.Reston.Va.US>; meta-sig at python.org
<meta-sig at python.org>; Python/C++ SIG <c++-sig at python.org>; dubois1 at llnl.gov
<dubois1 at llnl.gov>
Date: Wednesday, December 17, 1997 9:47 AM
Subject: Re: [C++-SIG] RE: [META-SIG] Terminating comatose SIGs


>>>>>> "GF" == Geoffrey M Furnish <furnish at xdiv.lanl.gov> writes:
>
>
>    GF> If however, the PSA is willing to host discussion about
>    GF> binding Python to C++, then let's let this be the last time
>    GF> this issue has to be redecided.
>
>Here's two pieces of information that have a direct bearing on
>the (future) impact of the Python/C++ Sig:
>
>1) As of last night, an expression template array library
>   (http://monet.uwaterloo.ca/blitz) that
>   pushes non-EDG-based C++ compilers beyond their limits works with
>   a GNU compiler (http://www.cygnus.com/egcs).
>
>2) Mumit Khan has succeeded in porting egcs-1.0 to windows95/NT using both
>   the cygwin and mingwin dlls. (http://www.xraylith.wisc.edu/~khan).
>
>This means:
>
>a) that the number of people able to compile and experiment with a
>   C++-extended python is about to increase by several orders of
>   magnitude.
>
>b) that the numerical performance increase made possible by expression
>   templates should focus attention on standard-conformance, STL
>   techniques, dead-code removal, incremental compilation, etc.  The
>   better egcs gets in these areas, the more compelling the advantages
>   of the LLNL-modified python becomes.
>
>So the no-compromises approach of GF and PDB is about to pay off, and
>it would be short-sighted to shut down the C++ sig 2 weeks after the
>approval of the draft standard and the release of a near-standard
>conforming free compiler.
>
>Regards, Phil
>
>
>


_______________
C++-SIG - SIG for Development of a C++ Binding to Python

send messages to: c++-sig at python.org
administrivia to: c++-sig-request at python.org
_______________