Hi, Jim<br><br>I didn't work on iGeom level before, and wasn't very sure what the spec's are. I did add a function declaration in iGeom.h yesterday though. Not sure if this affected the Python build. Please let me know if you'd rather to make any changes for it.<br>
<br>Thanks.<br><br>Jane<br><br><br><div class="gmail_quote">On Thu, Sep 29, 2011 at 5:50 PM, James Porter <span dir="ltr"><<a href="mailto:jvporter@wisc.edu" target="_blank">jvporter@wisc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Even though the iGeom spec isn't as firm as iMesh's, perhaps we should put our extra, non-standard functions in a separate header file. This would make it easier to write iGeom code that works on multiple implementations, and would help me write Python bindings for iGeom that work with other implementations too (currently, if any function that is bound to Python doesn't exist in the iGeom implementation, it refuses to load the .so).<br>
<br>
Thoughts/opinions on this?<br>
<br>
- Jim<br>
</blockquote></div><br>