I want to thank Ivan and Bill for useful advice. I eventually found my memory
mistake,
which was of the 'obvious once you see it' variety. Ivan's note that it
appeared to be in
a small allocation was correct.
> I've hit a roadblock debugging a new update to the survival package. I do
>
The trace() function is very nice for setting breakpoints or other
debugging code in functions and methods, but its interface is
confusingly complicated.
For example, there was a question on StackOverflow recently that led to
this observation:
trace(stats::predict.lm, edit = TRUE)
will
Hello all:
Thank you both for your advice.
I attempted to upload the latest version to CRAN, and again received
the notification that the package did not pass.
It seems there are no warnings or errors (only 2 notes) on windows
Removing (or moving to inst) the unrecognized file should be sufficient.
Duncan Murdoch
On 19/02/2024 7:27 a.m., Package Maintainer wrote:
Hello all:
Thank you both for your advice.
I attempted to upload the latest version to CRAN, and again received
the notification that the package did not
Dear Duncan:
Thank you for the feedback about that. I have removed the unrecognized
file and resubmitted the package. Thanks again.
Kind regards,
LAR
On Mon, Feb 19, 2024 at 2:20 PM Duncan Murdoch wrote:
>
> Removing (or moving to inst) the unrecognized file should be sufficient.
>
> Duncan
