[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bindings
Subject: [Kde-bindings] Smoke call policy question
From: Roberto Alsina <ralsina () kde ! org>
Date: 2006-10-25 20:54:34
Message-ID: 200610251754.35002.ralsina () kde ! org
[Download RAW message or body]
A little over a year after I first looked at Smoke, I am looking again, this
time using Boost::Python and Pyste, and... of course I am not geting it ;-)
Specifically, what's the ownership semantics of calling stuff in smokelib?
If I call SmokeBinding::className() who owns the char *?
If I call Smoke::cast() who owns the returned object?
It would be specially useful if it could be explained in terms used by Boost:
http://www.boost.org/libs/python/doc/tutorial/doc/html/python/functions.html#python.call_policies
I can probably figure it out by trial and error, of course, but maybe someone
can figure it out quickly :-)
--
("\''/").__..-''"`-. . Roberto Alsina
`9_ 9 ) `-. ( ).`-._.`) ralsina@kde.org
(_Y_.)' ._ ) `._`. " -.-' KDE Developer (MFCH)
_..`-'_..-_/ /-'_.'
(l)-'' ((i).' ((!.' Buenos Aires - Argentina
Feynman's problem solving algorithm: write down the problem->
think very hard -> write down the answer.
_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic