MOAB: Mesh Oriented datABase
(version 5.5.0)
|
A few of the functions in iMesh support arbitrary options passed as a character string, called an 'Option String'. The format of and handling of an Option String is as follows...
For example, consider the Options String
"grummp:silant FMDB:TwoPhaseIO moab:mpiio_hints\ foo\:bar"
In the above example, the space serves as the delimiter character between multiple options in the string. The colon serves as the implementation-name/option separator character. Because options are required to be insensitive to case, the caller is free to use case as a word separator as in 'TwoPhaseIO' and even in the implementation name, as in 'FMDB:', although 'fmdb:twophaseio' and 'fmdb:TWOPHASEIO' would all have the same effect. In the moab option, both the separator character and delimiter character appear in the option and so are pre-pended (e.g. escaped) with the backslash character.
GRUMMP will silently ignore the FMDB: and moab: options because they do NOT match on the implementation name part. However, GRUMMP may optionally error out, or warn or silently ignore 'grummp:silant' (it was supposed to be spelled 'silent') as an invalid option.
Note that iMesh itself currently does not define any options. In order to discover options a given implementation defines, users are directed to the developers of the respective implementations.