On Wed, 10 Dec 2008, Roy Stogner wrote:
> Even after we come up with a new API, there's probably other places in > mesh/*.C where the "one id per side" assumption is being made. It was > in xdr_io.C that I hit that bug, for instance: > XdrIO::write_serialized_bcs() gets called with > n_bcs==n_boundary_conds(), the total number of boundary conditions > set. But it only writes out one id per side (all it can get from > BoundaryInfo::boundary_id()), and it asserts that the total number of > ids it encounters this way must be equal to the n_bcs from before. Hmm... for right now, I think all I'm going to do is fix BoundaryInfo::add_side() to avoid adding the *same* id to the same side twice. That will still allow other users to add different ids to the same side, it'll be enough to avoid the XdrIO bug for my problems, and it'll be a much quicker fix than deciding what the right API for multi-id sides is. --- Roy ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
