Re: Re: Pros and Cons of using existing runtimes?
Mukhsein Johari <[email protected]> Wed, 18 Aug 2004 13:18:41 +0100 (BST)
| Newsgroups | gmane.comp.lang.prothon.user |
|---|---|
| Message-ID | <[email protected]> |
--- Roger Binns <[email protected]> wrote: > Mukhsein Johari wrote: > > As a side note: For libs, you said yourself that > the > > interesting python libs are C extensions anyway - > why > > not simply do a 'swig' to prothon? Et voila, > instant > > libs! Why is this no longer a solution to your > libs > > problem? > > If you are referring to the SWIG program as at > swig.org then I was refering to it but not directly. I meant "to use the same approach" but it appears that that might not be the best way after all. See below. > it isn't as simple as that. It never is :-) [snip] > They code against the interpretter C API. You also > can't do without that layer since code somewhere has > to deal with issues such as allocating objects and > who owns memory. Mark, could a prothonized wrapper/adapter for the python interpreter C API not do the job (of enabling the use of these C extention libs)? Or are the interpreters so completely different that the whole thing would result in some complicated mess? If it is workable, would this path be more or less work then going the .NET route? ________________________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html