From therne@u @ending from m@yo@edu  Tue May  1 23:09:44 2018
From: therne@u @ending from m@yo@edu (Therneau, Terry M., Ph.D.)
Date: Tue, 01 May 2018 16:09:44 -0500
Subject: [Rd] issue with model.frame()
In-Reply-To: <23272.51944.116829.707510@stat.math.ethz.ch>
References: <bb6fa2$9b935h@ironport10.mayo.edu>
 <EF41437C-933A-44C7-86C0-992953B39E9E@ucsd.edu>
 <23272.51944.116829.707510@stat.math.ethz.ch>
Message-ID: <bb6fa2$9beirt@ironport10.mayo.edu>

I want to add that the priority for this is rather low, since we have a couple of work 
arounds for the user/data set in question.  I have some ideas about changing the way in 
which ridge() works, which might make the problem moot.  The important short-term result 
was finding that it wasn't an error of mine in the survival package. :-)

Add it to your "think about it" list.

Terry


On 05/01/2018 03:15 PM, Martin Maechler wrote:
> What version of R is that ?  In current versions it is
> 
>      varnames <- vapply(vars, deparse2, " ")[-1L]
> 
> and deparse2() is a slightly enhanced version of the above
> function, again with  'width.cutoff = 500'
> 
> *BUT*  if you read  help(deparse)  you will learn that 500 is the
> upper bound allowed currently.  (and yes, one could consider
> increasing that as it has been unchanged in R since the very
> beginning (I have checked R version 0.49 from 1997).
> 
> On the other hand, deparse2 (and your older code above) do paste
> all the parts together  via  collapse = " "  so I don't see
> quite yet ...
> 
> Martin




[Rd] issue with model.frame()
Therneau, Terry M., Ph.D.