[Rd] Ah I've got it now .Thanks! RE: Understanding why "no metadata object found ... not exported?" warnings from the methods package exist, and what they mean

2015-03-13 Thread Geoff Lee
#x27;ll leave well enough alone. Many thanks for helping me learn about this. Geoff PS Apologies if I have sent too much to the list about this topic - if so let me know (gently please), so I can be better behaved in the future. -Original Message- From: Geoff Lee [mailto:geoff.le...@gm

Re: [Rd] Understanding why "no metadata object found ... not exported?" warnings from the methods package exist, and what they mean

2015-03-13 Thread Geoff Lee
n Chambers [mailto:j...@r-project.org] Sent: Saturday, 14 March 2015 8:11 AM To: Geoff Lee Cc: r-devel@r-project.org Subject: Re: [Rd] Understanding why "no metadata object found ... not exported?" warnings from the methods package exist, and what they mean On looking more closely, the purpose

[Rd] Understanding why "no metadata object found ... not exported?" warnings from the methods package exist, and what they mean

2015-03-12 Thread Geoff Lee
Hi I am seeking to understand why the methods package (to be specific `methods:::.findOrCopyClass` when called by `setIs` when called by `setClass`) emits a warning message such as ` class "SpatialLinesNULL" is defined (with package slot 'rgeos') but no metadata object found to revise subcl

[Rd] loadNamespace and versionChecking and the otherpackage::otherfun syntax

2014-12-20 Thread Geoff Lee
This is an enquiry not so much about what the code for loadNamespace does, but rather about the intent and design of loadNamespace, and how it interacts with the `::` function, which seems to me to follow a slightly different philosophy. It is not an urgent question - the issue that started me w

Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)

2014-11-28 Thread Geoff Lee
system. Hoping this makes sense, and helps someone else later on down the track Geoff PS Along the way I had a problem with devtools and roxygen2 - it was my error! I had a typo - a backtick ` when I should have had a single quote ' in a roxygen2 comment :-( -Original Mes

Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)

2014-11-27 Thread Geoff Lee
in of the journey, so I'll keep going) -Original Message- From: Duncan Murdoch [mailto:murdoch.dun...@gmail.com] Sent: Thursday, 27 November 2014 9:21 PM To: Geoff Lee; r-devel@r-project.org Subject: Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when vers

Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)

2014-11-26 Thread Geoff Lee
sage- From: Duncan Murdoch [mailto:murdoch.dun...@gmail.com] Sent: Thursday, 27 November 2014 12:09 PM To: Geoff Lee; r-devel@r-project.org Subject: Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked) On 26/11/2014, 7:

Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)

2014-11-26 Thread Geoff Lee
, 27 November 2014 10:57 AM To: Geoff Lee; r-devel@r-project.org Subject: Re: [Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked) Summary: I think you've found a bug. On 26/11/2014, 5:39 PM, Geoff Lee wrote: > Hi

[Rd] Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)

2014-11-26 Thread Geoff Lee
Hi I'm still exploring the R programming universe, so if this is being asked in the wrong place, or in the wrong way (e.g. too verbose or lacking in crucial detail or in the wrong format) please let me know I am trying to understand when the version constraints for packages which appear in