<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73">
<TITLE>RE: [Pyrex] Extension types</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Lenard Lindstrom wrote:</FONT>
</P>
<P><FONT SIZE=2>> Swig is for wrapping existing C libraries with as little fuss as possible. The interfaces </FONT>
<BR><FONT SIZE=2>> it generates can be customized if you are willing to spend the time studying the </FONT>
<BR><FONT SIZE=2>> documentation.</FONT>
</P>
<P><FONT SIZE=2>> Pyrex is for writing extension modules from scratch, though naturally it can also be </FONT>
<BR><FONT SIZE=2>> used to create wrappers. But I would try writing the module in pure Python if </FONT>
<BR><FONT SIZE=2>> possible and only make it an extension module if performation or memory is an </FONT>
<BR><FONT SIZE=2>> issue.</FONT>
</P>
<P><FONT SIZE=2>On this point I don't agree. I have written several wrappers for python in pyrex for existing c libraries and also tried to do the same in swig. I always came up against a brick wall in relation to callbacks. Where pyrex really shines is in allowing you to mix python and c-like syntax to achieve the needed symbiosis. I don't believe swig can ever be a 'quick and dirty' approach.</FONT></P>
<P><FONT SIZE=2>Grant M.</FONT>
</P>
</BODY>
<!--[object_id=#infocomp.com#]--><P><FONT face=Arial color=#808080 size=1>Important notice: This message is intended for the individual(s) and entity(s) addressed. The information contained in this transmission and any attached, may be confidential and may also be the subject of legal privilege, public interest immunity or legal professional privilege. Any review, retransmission, dissemination or other use of, taking of any action in reliance upon this information by person or entities other than the recipient is prohibited and requires authorization from the sender. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person) you may not copy or deliver this message to anyone. In such cases you should destroy this message and kindly notify the sender by reply email. </FONT></P>
<P><FONT face=Arial color=#808080 size=1>WARNING: Although Infocomp has taken reasonable precautions so that no viruses are present in this e-mail, the company cannot accept responsibility for any loss or damage arising from the use of e-mail attachments.</FONT></P></HTML>