From fd48802e2e8f5ec47aabaa6156bcbf437f413ce2 Mon Sep 17 00:00:00 2001 From: Salvatore Filippone Date: Fri, 2 Oct 2009 08:04:28 +0000 Subject: [PATCH] Fixed README. --- base/modules/README.F2003 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/base/modules/README.F2003 b/base/modules/README.F2003 index c1d7815e..ade965aa 100644 --- a/base/modules/README.F2003 +++ b/base/modules/README.F2003 @@ -8,7 +8,7 @@ Design principles for this directory. format. Thus we have a three-level inheritance chain: i. The base object, defining the methods to set/query the various - properties, and allocate and a free. Some of the property + properties, and allocate and free. Some of the property getters/setters, allocate and free depend on the storage format, so at this level they will just throw an error. ii. The X_base_object, where X=s,d,c,z thus defining the @@ -70,7 +70,7 @@ Design principles for this directory. conceivable storage representation provides just 2 conversion routines, avoiding quadratic explosion. But since all have to provide them, the to_coo/from_coo is defined in d_base_mat_mod - together with d_coo_sparse_mat, which enjoys the "eldest child" + together with d_coo_sparse_mat, which enjoys the "crown prince" status with respect to all the other types derived from d_base_sparse_mat (its "siblings").