[MOAB-dev] Changing the options format in iMesh
Tim Tautges
tautges at mcs.anl.gov
Mon Nov 15 12:30:39 CST 2010
On 11/15/2010 12:18 PM, Jason Kraftcheck wrote:
> On 11/15/2010 12:13 PM, James Porter wrote:
>> In order to be compatible with the iMesh spec, we need to change the
>> options format. Currently, it seems that MOAB uses the old iMesh-defined
>> options syntax. Should we continue to support this syntax, or should
>> MOAB use the new iMesh syntax? (Or maybe MOAB should have its own
>> syntax?)
>>
>
> MOAB already has its own syntax and I don't see any advantage to changing it.
>
>
>> For reference, the new way is "impl1:opt1 impl2:opt2", e.g. "moab:silent
>> moab:foobar". If MOAB got its own syntax instead of just doing this, I'd
>> expect the options to look like "silent foobar" by the time it got to
>> MOAB.
>
> That should actually be "; silent foobar" when passed to MOAB.
Wait, I thought with MOAB the starting delimiter was optional... and if they're two separate options, I'd expect
"silent;foobar", no?
- tim
>
>> Options for other implementations would be stripped at the iMesh
>> level.
>
> This seems like the obvious place to do so, as there are many iMesh
> implementations but only one MOAB implementation. An implementation prefix
> at the MOAB level wouldn't make sense.
>
> - jason
>
>
>
>
--
================================================================
"You will keep in perfect peace him whose mind is
steadfast, because he trusts in you." Isaiah 26:3
Tim Tautges Argonne National Laboratory
(tautges at mcs.anl.gov) (telecommuting from UW-Madison)
phone: (608) 263-8485 1500 Engineering Dr.
fax: (608) 263-4499 Madison, WI 53706
More information about the moab-dev
mailing list