Hi all,

We've accreted a few different print methods for our SparseMatrix and
NumericVector classes over the years.  For SparseMatrix there are
print(), print_personal(), and print_matlab() methods; for
NumericVector there are print(), print_global(), and print_matlab()
methods.  For the DenseMatrix as well, there are print() and
print_scientific() methods.

I now need to add one more format for SparseMatrices/NumericVectors.
Does it make sense to add yet another print method to the base classes
(which initially won't even have implementations for all the
subclasses)?  To me it seems cleaner to combine everything into a
single print(FormatType) interface, with a new enum defined for the
different possible matrix and vector file formats.  We can even easily
remain backwards-compatible by putting deprecated() messages in the
existing print_yyy routines and then calling the correct
print(FormatType).  Would there be any objections to me doing this?

-- 
John

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to