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

[Jason Kraftcheck]

Tim Tautges wrote:
> 
> 
> Jed Brown wrote:
 >
> 
>> Why does CGM use different options delimiters (":,\n\t") than MOAB
>> (";")?  I have discovered "ENGINE=OCC" for iGeom_newGeom and "TYPE=OCC"
>> for iGeom_load by reading the source, but are there other options to be
>> aware of?
>>
> 
> Likely that MOAB got updated and CGM didn't; Jason, can you fix this one?
> 

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.)

- jason