res wrote:
>
'bool Initialize (iObjectRegistry*)' is also contained in iComponent and
called after a plugin is loaded, to initialize the plugin. The iScript
method was probably deprecated because it appears pretty much superfluous.
Indeed.
One way would be to make an interface "iPythonScriptValue" or so that
contains a method to query Py-specific things. The scripting module
would query for that interface if needed, and get the "literal" value if
present, and bail out or try to make do with the data it has if it not
present.
For Perl I defined dummy interfaces in the plugin header (so they are
only available to the plugin) that inherit from iScriptObject and
iScriptValue, which are then inherited by the implementation classes.
Then I query the dummy interface and if it succeeds, static cast to a
pointer to the implementation class. You can see this with the
iScriptObject which is already in CVS (class csPerl5::Object and method
csPerl5::Query()), although it's still using the old-style SCF macros.
Neutral Robot Boy wrote:
it would be nice to see all those overloaded functions in
iScript/iScriptObject get deleted, BUT: doing so seems to really badly
break cspyth.cpp, which is generated by swig.
Break how? It might just be the %rename directives (pythpre.i 46-49)
that need removing.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Crystal-main mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: mailto:[EMAIL PROTECTED]
