Right now a user can interface with the System class by providing up to five
function pointers -
(1) initialization
(2) assembly
(3) constraints
(4) QOI
(5) QOI derivative
What do you think about optionally taking pointers to a class derived from
some pure virtual class(es):
class MyAssembly: public libMesh::System::UserAssembly,
public libMesh::System::UserInitialization
{
virtual void initialize();
virtual void assemble();
}
The user could create a class for each action or put multiple functions in
once class as shown above. That seems useful enough to be a reason to avoid
functors.
I'd never dream of removing the old function pointer approach, but perhaps
to provide this as an alternative.
Thoughts?
-Ben
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
