Skip to content

[R-pkg-devel] Warning: rBind is deprecated-- but I don't call it

3 messages · William Revelle, Alexandre Courtiol, Duncan Murdoch

Original
William Revelle
# 
Dear friends,

When testing my latest version of psych on win.builder, I keep getting the following Warning:

* checking installed files from 'inst/doc' ... OK
* checking files in 'vignettes' ... OK
* checking examples ...
** running examples for arch 'i386' ... [32s] WARNING
Found the following significant warnings:

  Warning: 'rBind' is deprecated.
Deprecated functions may be defunct as soon as of the next release of
R.
See ?Deprecated.
** running examples for arch 'x64' ... [39s] WARNING
Found the following significant warnings:

  Warning: 'rBind' is deprecated.
Deprecated functions may be defunct as soon as of the next release of
R.
See ?Deprecated.
* checking for unstated dependencies in vignettes ... OK

I know that rBind is deprecated, but I don?t call it.


I have searched my code and as far as I can tell, I do not use rBind (nor cBind).   Nor do any of my examples.

Any help would be appreciated.

Thanks.

Bill


William Revelle		   personality-project.org/revelle.html
Professor			          personality-project.org
Department of Psychology www.wcas.northwestern.edu/psych/
Northwestern University	   www.northwestern.edu/
Use R for psychology         personality-project.org/r
It is 2   minutes to midnight   www.thebulletin.org
Alexandre Courtiol
# 
Hi William,
Perhaps you use rBind indirectly...
I don't know the best way to check that, but I would try to set a
debug(rBind) before running some of your code in an interactive session.
If any function uses rBind, you should notice as it will launch the
debugger.
Better ideas are welcome.
++

Alex
On 21 March 2018 at 19:36, William Revelle <lists at revelle.net> wrote:

            

      
      
      
    

        

      
      
    

        

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Duncan Murdoch
    

    

      
      #
    

  


  

      
On 21/03/2018 2:48 PM, Alexandre Courtiol wrote:

            

      
      
      
    

        
That's a good idea; setting options(warn=2) (so the warning becomes an 
error) might also be good. To narrow the search, look at the log file 
from the check.  Specifically, if checking package "foo", look at 
foo-Ex.Rout for the output from running all the examples (and which 
should contain the warning at an informative spot), or foo-Ex.R if you 
want all the code that was run to get that output.

Duncan Murdoch