On 10.03.2016 15:49, Duncan Murdoch wrote:> On 10/03/2016 8:27 AM, Kirill M?ller wrote: >> I can't seem to reliably obtain parse data via getParseData() for >> functions from installed packages. The parse data seems to be available >> only for the *last* file in the package. >> >> See [1] for a small example package with just two functions f and g in >> two files a.R and b.R. See [2] for a documented test run on installed >> package (Ubuntu 15.10, UTF-8 locale, R 3.2.3). Same behavior with >> r-devel (r70303). >> >> The parse data helps reliable coverage analysis [3]. Please advise. > > You don't say how you built the package. Parse data is omitted by > default. > > Duncan MurdochI install using R CMD INSTALL ., and I have options(keep.source = TRUE, keep.source.pkgs = TRUE) in my .Rprofile . The srcrefs are all there, it's just that the parse data is not where I'd expect it to be. -Kirill>> >> Best regards >> >> Kirill >> >> >> [1] https://github.com/krlmlr/covr.dummy >> [2] http://rpubs.com/krlmlr/getParseData >> [3] https://github.com/jimhester/covr/pull/154 >> >> ______________________________________________ >> R-devel at r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel >
On 10/03/2016 9:53 AM, Kirill M?ller wrote:> > On 10.03.2016 15:49, Duncan Murdoch wrote: > > On 10/03/2016 8:27 AM, Kirill M?ller wrote: > >> I can't seem to reliably obtain parse data via getParseData() for > >> functions from installed packages. The parse data seems to be available > >> only for the *last* file in the package. > >> > >> See [1] for a small example package with just two functions f and g in > >> two files a.R and b.R. See [2] for a documented test run on installed > >> package (Ubuntu 15.10, UTF-8 locale, R 3.2.3). Same behavior with > >> r-devel (r70303). > >> > >> The parse data helps reliable coverage analysis [3]. Please advise. > > > > You don't say how you built the package. Parse data is omitted by > > default. > > > > Duncan Murdoch > > I install using R CMD INSTALL ., and I have options(keep.source = TRUE, > keep.source.pkgs = TRUE) in my .Rprofile . The srcrefs are all there, > it's just that the parse data is not where I'd expect it to be. >Okay, I see what you describe. I'm not going to have time to track this down for a while, so I'm going to post your message as a bug report, and hopefully will be able to get to it before 3.3.0. Duncan Murdoch
On 10.03.2016 16:05, Duncan Murdoch wrote:> On 10/03/2016 9:53 AM, Kirill M?ller wrote: >> >> On 10.03.2016 15:49, Duncan Murdoch wrote: >> >> >> I install using R CMD INSTALL ., and I have options(keep.source = TRUE, >> keep.source.pkgs = TRUE) in my .Rprofile . The srcrefs are all there, >> it's just that the parse data is not where I'd expect it to be. >> > > Okay, I see what you describe. I'm not going to have time to track > this down for a while, so I'm going to post your message as a bug > report, and hopefully will be able to get to it before 3.3.0. >Thanks. A related note: Would it be possible to make available all of first_byte/last_byte/first_column/last_column in the parse data, for easier srcref reconstruction? -Kirill