Re: [Libmesh-devel] MeshBase::point_locator() isn't thread-safe

[Roy S. <roy...@ic...>]

On Fri, 22 Apr 2011, Derek Gaston wrote:

> 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! ;-)

I made yet-a-third API change; some const correctness stuff in
PeriodicBoundaries.

It's all done, working on my initial tests, and committed.  In the
event that all our big test suites pass tonight then I'd like to call
this 0.7.1.  Could you guys run your tests too ASAP?

Thanks,
---
Roy