On Fri, 25 Jan 2013, Derek Gaston wrote:
Now - I have a question. I was going to call this new system
"MeshTransfer"... but I'm now thinking that might not be the best
name (we're not transferring meshes... we're transferring/mapping
values). So how about "SolutionTransfer" and I'll put it in
src/solution_transfer and include/solution_transfer.
Anyone have a preference?
solution_transfer sounds like an improvement for the dir name.
SolutionTransfer is the abstract base class name that'll eventually
cover both your and Ben's new capabilities, right? If so then great.
BTW - I'm done with the interface... and I did go ahead and add
System to Variable... it made the interface nice and tidy!
Yeah, this was the right way to go. With the system-specific variable
number already a member of Variable, keeping the system-specific
System& (or System* ?) out *looks* more modular, but it wasn't really.
---
Roy
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
