rare bad bug in sys.function() {or match.arg()} (PR#1409)
Luke Tierney <luke@stat.umn.edu> writes:
On Fri, Mar 22, 2002 at 11:39:10PM +0100, Peter Dalgaard BSA wrote:
maechler@stat.math.ethz.ch writes: This looks suspiciously like the same issue as PR#921. Did someone have plans to change the context stack handling so that we could have a "real" sys.function()? To quote my own followup to PR#921: "The problem is that we only actually store the call in the context structure, not the function, so sys.function has to grab the call, take the 1st element, and reevaluate it in the parent frame."
I have it on my list but won't get to it for 1.5.
OK. Obvious stopgap measure inserted for now (use findVar1, testing for FUNSXP). Still won't handle the (f(foo))(bar) cases properly, of course.
O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'_ --- Dept. of Biostatistics 2200 Cph. N (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - (p.dalgaard@biostat.ku.dk) FAX: (+45) 35327907 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._