Joe, thanks
Yes, I am on the P4D mailing list :) What you didn't say was that the "python for delphi" extensions are *awesome*. full two-way communication, and you get it all by drag&dropping a little component widget onto your form in the IDE. Amazing.
However...
Dll's can be used by things other than python, which is the main reason why we would go that route. However, with all the .NET hoopla, maybe IronPython and a .NET dll would be the way to go in the future. I'm still a little uneasy about adopting .NET as a standard just yet...
I should give it some more thought anyways.
Thanks again Caleb
On Wed, 09 Feb 2005 12:38:37 -0500, Joe Francia <[EMAIL PROTECTED]> wrote:
Caleb Hattingh wrote:As you might imagine, I think about this constantly. However, there are many other issues that make it complicated, such as having to work in a team where the average guy knows pascal well (we're just a bunch of chemical engineers), but has never even heard of python. Plus, were I to go this type of route, I would almost definitely code the binary modules in Delphi or FreePascal, make a DLL and use ctypes to call it. I do not know C and have no desire to learn now :) On the other hand, I know pascal quite well. keep well Caleb
You could always code Python extensions directly in Delphi:
http://membres.lycos.fr/marat/delphi/python.htm http://www.atug.com/andypatterns/PythonDelphiLatest.htm
Demo09 (look in demodll.dpr & module.pas) in the download tells you how.
Peace, Joe
-- http://mail.python.org/mailman/listinfo/python-list
