Those are small parts of the calculation, not the whole thing. The original point was that optim() is a very thin wrapper around the code to do the optimization. I just don't see a need to make it more complicated so it can be used to wrap other methods. Authors of new optimization methods can just create new functions, following the pattern set by optim(), and it will be easier for almost everyone.
Duncan Murdoch On 06/08/2007 11:18 PM, Andrew Robinson wrote: > ... Variance and correlation model classes in nlme. > > Cheers > > Andrew > > On Mon, Aug 06, 2007 at 09:55:38PM -0500, hadley wickham wrote: >> On 8/4/07, Duncan Murdoch <[EMAIL PROTECTED]> wrote: >>> On 04/08/2007 2:53 PM, Gabor Grothendieck wrote: >>>> The example of generic functions. >>> Show me an example where we have a list of ways to do a calculation >>> passed as an argument (analogous to the method argument of optim), where >>> the user is allowed to add his own function to the list. >> Bin width selection in hist? Family functions for glm? Those come >> quickly to my mind, but I'm sure there are others. >> >> Hadley >> >> ______________________________________________ >> R-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel > ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
