> Sure, no problem. It sounds like you have something specific in mind -- > and like you know the library better than I do. Would you be able to > create a patch?
I've only started using it recently, although I have noticed a few issues of varying importance. To be honest, most of these should probably be addressed upstream and having a divergent Debian version, even if it is superior is probably a bad thing. Anyway, these are the various issues: - no #ifdef header guards to prevent multiple inclusion. - #define of REAL conflicts with other headers. In my case, the OpenMPI ones. At the very least, making it a typedef might make the errors easier to understand without damaging compatibility although I think having such #defines for REAL and VOID is something to avoid. - A #ifdef __cplusplus guarded extern "C" construct would be nice for C++ users. - The Debian-specific API exposure might cause issues. In my case, I had classes/variables named triangle, mesh and vertex. I don't fully understand why so much of the triangle API was exposed. Does OpenCASCADE depend upon Debian specific modifications? Would it make more sense to put the extended API in a header which then includes triangle.h? I'm happy to make any patches if you think some of these issues should be addressed in the Debian version. Francis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
