Newly adding some output to a code, I forgot to provide the XdrMODE argument to EquationSystems::write()... which then raised the question: why do we need to provide an XdrMODE argument to EquationSystems::read() and ::write(), exactly? read() ought to be able to assume READ or DECODE, write() ought to be able to assume WRITE or ENCODE, and we can hunt for .xda vs .xdr in the filename to decide between READ/WRITE and DECODE/ENCODE. Anyone see anything I'm missing?
I'm going to leave the existing APIs untouched (maybe someone wants to use filenames without our extensions or with misleading extensions, and of course we don't want to break existing code) but I'll add an interface that does the inferences and then hands off to the existing API. --- Roy ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
