> I would like to hear your and Ben's views on what the default should > be; it's probably inconvenient for you to keep it switched to unsigned > int if we're still using unsigned char.
That is interesting. I would think that since unsigned char suited for most users needs till now, that should be the default. But if a user needs to use more material ids based on subdomain id, then he should have an easy way to change it. Refer to my previous email about this. May be typedefing would be straight forward enough for a user to change as long as he knows where to find it... What do you think ?! On Wed, Feb 11, 2009 at 4:01 PM, Roy Stogner <[email protected]> wrote: > > On Wed, 11 Feb 2009, Roy Stogner wrote: > >> On Wed, 11 Feb 2009, Vijay S. Mahadevan wrote: >> >>> Do have a look at the patch and if everything looks good (conventions >>> and definition placement), do commit this. >> >> Looks good so far; let me test a couple things and I'll commit it. > > I would like to hear your and Ben's views on what the default should > be; it's probably inconvenient for you to keep it switched to unsigned > int if we're still using unsigned char. But, thanks to structure > padding, an unsigned short or unsigned int is likely to take up 4 more > bytes per element, and Ben sounds quite concerned about memory use > lately. > > Also, I need to add some comment up at the definition about what types > are allowed; it looks like PackedElem means that (at least in > parallel) we're still limited to types that can static_cast to and > from int successfully, and the I/O classes probably restrict us to > types that can operator= to and from int successfully. I guess that's > not a *bad* thing; it'll dissuade people from making subdomain ids > into a bitset or a custom class or something else that'll end up > backfiring on them. > --- > Roy > ------------------------------------------------------------------------------ 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
