Flipping through feature requests for a libMesh-based application, I noticed this one: when output files with directory paths (e.g. outputdirectory/outputsubdirectory/outputfile) are requested, and when at runtime outputdirectory and/or outputsubdirectory don't yet exist, they ought to be created. (the current behavior is a libmesh_file_error() exception)
Not sure when I'm going to get around to this item, but when I do, would anyone find it useful as a libMesh feature? If so, should it be standard behavior, or default behavior that can be disabled with a parameter to the write methods, or non-default behavior that can be enabled with a parameter to the write methods? --- Roy ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
