Simply add a definition for this variable to the source for your package,
e.g.;
.Last.make.date <- NULL
And the warning should go away.
-g
On 6/30/08 11:44PM , "Rolf Turner" <r.turner at auckland.ac.nz>
wrote:
>
>
> I have written a function make.fun(), which I keep in my personal
> ``miscellaneous'' package. It searches the current working
directory
> for files named ``*.R'' and sources them if their modification date
> is later than the date stored in ``.Last.make.date''. (The
variable
> .Last.make.date then gets updated.) The function checks whether
> .Last.make.date exists before comparing its value with the modification
> dates of the *.R files.
>
> When I do R CMD check on my ``miscellaneous'' package, I get a
``NOTE''
> (not even a warning!) to the effect:
>
> ``no visible binding for global variable '.Last.make.date'
>
>
> Is this something that I should worry about at all? Am I running any
> risk by this procedure? Is there a better way to check whether code file
> have modified sufficiently recently that they need to be re-sourced?
>
> Thanks for any tips. (But no asparagus, please! :-) )
>
> cheers,
>
> Rolf Turner
>
> ######################################################################
> Attention:\ This e-mail message is privileged and confid...{{dropped:9}}
>
> ______________________________________________
> R-help at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
--
Gregory R. Warnes, Ph.D
Program Director
Center for Computational Arts, Sciences, and Engineering
University of Rochester
Tel: 585-273-2794
Fax: 585-276-2097
Email: gregory.warnes at rochester.edu