Roy, What kind of configure options would you like for this task. It appears we don't have many argument based options but it makes sense for this case.
--subdomain-id-bytes=[1,2,4] Alternatively we could put in separate options for each of these cases consistent with most of the existing options --enable-subdomain-id-8 --enable-subdomain-id-16 --enable-subdomain-id-32 Cody On Jun 2, 2011, at 9:56 AM, Roy Stogner wrote: > > On Wed, 1 Jun 2011, Cody Permann wrote: > >> subdomain_id_type impacts on Elem Size: >> >> 8 bits: sizeof(Hex8) = 96 >> 16 bits: sizeof(Hex8) = 96 >> 32 bits: sizeof(Hex8) = 96 >> 64 bits: sizeof(Hex8) = 104 (just to verify) > > One other minor thought: the lack of growth going from 16 to 32 bits > makes it tempting to make 32 bits the default - however, if 16 bits is > sufficient for you I'd like to stick with that (unless the user makes > a configure-time decision to the contrary). I still fantasize about > adding anisotropic p adaptivity one day, and my various half-baked > ideas for doing so would use up the rest of the padding bytes in the > 16-bit-subdomain_id case or would tack another 8 bytes onto the > structure in the 32-bit-subdomain_id case. > --- > Roy ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
