I personally use ClassBase classes to mean "implementation base"
as in there is a pure (or almost pure) abstract class and then there
is a ClassBase class derived off of that which implements a lot of
shared functionality that a further derived leaf class can then
utilize. This doesn't happen
It looks like the MeshIO classes all work on MeshBase references
already. This would allow e.g.
es.get_mesh().write("foo.gmv");
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find proble
On Thu, 1 Nov 2007, John Peterson wrote:
> It looks like the MeshIO classes all work on MeshBase references
> already. This would allow e.g.
>
> es.get_mesh().write("foo.gmv");
Sounds like a good idea to me.
---
Roy
-
This