TITLE OF PAPER:         
URL OF PRESENTATION:    _URL_of_powerpoint_presentation_
PRESENTED BY:           Tamer Fahmy
REPRESENTING:           Vienna University of Technology

CONFERENCE:             PyCON 2004
DATE:                   20040324
LOCATION:               _venue_and_room_in_venue_

--------------------------------------------------------------------------
REAL-TIME NOTES / ANNOTATIONS OF THE PAPER:
{If you've contributed, add your name, e-mail & URL at the bottom}

wrapper generators
    swig
    sip
    boost.python (pyste)
    gcc_xml

c++ a hard lang to wrap?
    in/out params
    mapping of adv features into python (operator=, etc)
    operator/method overloading
    inheritance, templates, exceptions
    runtime system avail? use it! (autocasting)

pivy - pybinding for coin
  chosen approach (why swig)
  how he did it
    -includeall and fake_headers
    (some mumbo jumbo about having to stop his little app thing from
    generating python bindings for stdlib types like std::string, blah)
    got all the basic types right
        70% of work done
        typemaps and glue code!

    something gave him a headache. converting something 
    
pivy - pybinding for coin
    libswigpy (swig runtime lib)
    bridge to other bindings (pyqt)
        mixing swig and sip
        get pointer to obj
        watch out for ownership

sheesh, blinked and missed the last slide.

oop, second chance. 

conclusion
    c++ support improved lots in last 2 years
    gcc_xml as core for wrapper generators?
    common pointer exchange API standard for wrapper generators

Q: older libraries frequently have written their own collections. strings being one example. did you run into that, and how did you handle it?
A: swig interface to stl, easy. just remap it to basic python type. wrapped into lists, tuples, etc.

--------------------------------------------------------------------------
REFERENCES: {as documents / sites are referenced add them below}

--------------------------------------------------------------------------
QUOTES:

--------------------------------------------------------------------------
CONTRIBUTORS: {add your name, e-mail address and URL below}
Bob Kuehne, rpk@blue-newt.com, http://www.blue-newt.com
Mike Taylor, bear@code-bear.com
Linden Wright, lwright@mac.com

--------------------------------------------------------------------------
E-MAIL BOUNCEBACK: {add your e-mail address separated by commas }



--------------------------------------------------------------------------
NOTES ON / KEY TO THIS TEMPLATE:
A headline (like a field in a database) will be CAPITALISED
    This differentiates from the text that follows
A variable that you can change will be surrounded by _underscores_
    Spaces in variables are also replaced with under_scores
    This allows people to select the whole variable with a simple double-click
A tool-tip is lower case and surrounded by {curly brackets / parentheses}
    These supply helpful contextual information.

--------------------------------------------------------------------------
Copyright shared between all the participants unless otherwise stated...