On Apr 22, 2011, at 9:17 AM, Roy Stogner wrote: > How about another change: making the PointLocatorBase an argument to > PeriodicBoundaries::neighbor, Elem::periodic_neighbor, etc.? That's a > little uglier and it's more API breakage, and it's not necessary for > correctness, but it'll allow us to avoid constructing subordinate > PointLocatorTree objects (with empty caches) over and over again, > which ought to be good for efficiency.
Works for me. That kind of stuff can be arbitrarily complicated: it needs to be fast... and you figure it out once and just leave it alone (until someone changes the API! ;-) Derek ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
