> Alright. First, I'll make the change of type for sbd_id to unsigned > int in Elem.h and all other relevant files. I will include a patch of > this once I have tested that it works with my code.
To be clear, you mean a change to typedef unsigned short int subdoman_id_t; subdomain_id_t _sbd_id; or something like that? > Ben, if std::vector<blah> is not the way to go, then the idea behind > propagating MeshData's structure would also fall prey to all the same > issues as having a generic container in Elem. But this is how the > interface is already defined for MeshData ! The would it be elegant to > do something like what Roy suggested. This is really a semantic issue. I was thinking that my notional 'FatDofObject' would contain something like this std::vector<blah>, or a blah itself, or whatever... What I do not want to do is throw an unused vector in the base DofObject (or Elem), which is why I suggested the templates. But for a lot of reasons Roy's typedef makes more sense. -Ben ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
