On Apr 30, 2010, at 1:59 PM, Roy Stogner wrote: > Ah, but that's what typecasts are for!
Ewwww! > (joking!...) You'd better be! > I think the best you could do is overload the attachment methods, so > that one takes the first kind of function pointer and the other takes > the second, you store the two in different internal pointers, and then > at dispatch time you see which of the internal pointers are non-NULL. Double ewwww! Not to mention that we don't actually have setters for these things... we literally just do nonlinear_solver->residual = func_ptr! So to go down this path we would do: nonlinear_solver->new_residual_function_that_passes_more_info = func_ptr ;-) > Basically not worth it to avoid a tiny API compatibility breakage. > Especially when that breakage has the side benefit of punishing users > for not using DiffSystem. > (still joking! mostly! ...) Heh. Derek ------------------------------------------------------------------------------ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
