search for: allowdotasnam

...d no 'data' argument While the error message isn't especially helpful (as I *cannot* currently pass in a data argument), the problem is that terms.formula inside update.formula does not allow a dot in the RHS of 'old' unless either a 'data' argument is passed in or 'allowDotAsName=TRUE'. Thus, I'd like to suggest this change to update.formula to allow a dot in the RHS of old without (I believe) impacting any other behavior. - out <- formula(terms.formula(tmp, simplify = TRUE)) + out <- formula(terms.formula(tmp, simplify = TRUE, allowDotAsName=TRUE))...

I am working on a new package, one in which the user needs to specify the role that different variables play in the analysis. Where I'm stumped is the best way to have users specify those roles. Approach #1: Separate formula for each special component First I thought to have users specify each formula separately, like: new.function(formula=y~X1+X2+X3, weights=~w,

...of the range bars to be set (default unchanged at "light gray"). o Added tclServiceMode() function to the tcltk package to allow updating to be suspended. o terms.formula() no longer allows '.' in a formula unless there is a (non-empty) 'data' argument or 'allowDotAsName = TRUE' is supplied. We have found several cases where 'data' had not been passed down to terms() and so '.' was interpreted as a single variable leading to incorrect results. o New functions trans3d(), the 3D -> 2D utility from persp()'s example, and extendran...

...of the range bars to be set (default unchanged at "light gray"). o Added tclServiceMode() function to the tcltk package to allow updating to be suspended. o terms.formula() no longer allows '.' in a formula unless there is a (non-empty) 'data' argument or 'allowDotAsName = TRUE' is supplied. We have found several cases where 'data' had not been passed down to terms() and so '.' was interpreted as a single variable leading to incorrect results. o New functions trans3d(), the 3D -> 2D utility from persp()'s example, and extendran...