On Fri, 6 Jan 2012, Paul T. Bauman wrote: > In some of my development, I've run across a case where I'd like to only > access variables from FEMContext that do not change the > private data (e.g. interior_value). Thus, I would like to pass a const > reference to a FEMContext object and get some safety. The > attached makes these accessor methods const so I can work with const > FEMContext& objects. Builds against r5024 and make > run_examples ran fine. My described use case also compiles with the patched > version of the library. > > I'd be grateful if this made it into the library. Please let me know if there > are any problems.
This all looks like a big correctness improvement to me. I'm really tempted to make the Physics and QoI interfaces take const context objects now; presumably there's similar safety improvements possible in rbOOmit... I'm committing to trunk; but since the context objects get used in reduced_basis stuff as well as FEMSystem stuff I reserve the right to change or revert things if any of the rb developers scream. ;-) --- Roy ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
