Sounds like a reasonable change. I'd say go for it. -J
On Sun, May 11, 2008 at 10:57 PM, Roy Stogner <[EMAIL PROTECTED]> wrote: > > In the process of fixing ParallelMesh bugs, I've decided that the name > of the Elem::is_neighbor() method is a bit ambiguous. If > elemA->is_neighbor(elemB) is true, does that mean that > elemA->neighbor(somedirection) == elemB or does it mean the converse? > In an non-conforming adaptively refined mesh, neighborness isn't a > symmetric relation. > > Since the implementation of the function is to return true if and only > if elemA->neighbor(elemB), I've decided that has_neighbor() is a more > intuitive name. I'll be committing that (in a batch with some > ParallelMesh bugfixes) eventually. If anyone has a better name > suggestion, or if anyone wants to see is_neighbor() kept around > (temporarily or permanently) for API compatibility's sake, let me > know. > --- > Roy > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Libmesh-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
