[cgma-dev] Seg fault when loading OCC geometry with associations

[Jed Brown]

On Mon 2009-03-30 10:17, Jason Kraftcheck wrote:
> This is fixed, but probably not in quite the way it was requested.  The  
> behavior of MOAB's direct API (described above) is not the same as what  
> is required and implemented for the iMesh API.  As this bug was with the  
> iGeom API implementation for CGM, I have made it conform to the ITAPS  
> spec.
>
> The ITAPS interfaces specify no fixed or default separator character for  
> options strings.  They require that the first character of every passed  
> option string be an caller-specified separator character (even when the  
> string contains only one option and therefore no other separator  
> characters.)

Great.  If I choose the separation character to be ';' and always place
it first, then the same options format should work with both.  It would
help to document the available options somewhere (both for MOAB and
CGM), a list of options and a 1-line description would have saved me
some time.

Jane, I'm putting together a tidy test case to demonstrate the geometry
problem.

Jed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/cgma-dev/attachments/20090330/75c3aaa8/attachment.pgp>