On Thu, 5 Nov 2009, mark.braving...@csiro.au wrote:
Great-- thanks for the info.
For now, hopefully I can get the behaviour I want by sticking a .Call(
'R_lazyLoadDBflush'...) [as per 'detach'] before calling 'lazyLoad'. Seems to
work on my examples, but please let me know if you don't think
Great-- thanks for the info.
For now, hopefully I can get the behaviour I want by sticking a .Call(
'R_lazyLoadDBflush'...) [as per 'detach'] before calling 'lazyLoad'. Seems to
work on my examples, but please let me know if you don't think it'll work
generally-- if not, I could presumably crea
Here is a more stripped down variant generates and error on OS X for me:
mkEg <- function(tm) list(scrunge = as.POSIXct(tm))
extract <- function(db) {
e<- new.env()
lazyLoad(db, e)
as.list( e)
}
eg <- mkEg("2009-11-04 12:49:53")
eg1 <- mkEg("2009-11-0
Hi,
On 11/3/09 6:51 PM, mark.braving...@csiro.au wrote:
file.copy( 'd:/temp/Rdiff.Rd', 'd:/temp/scrunge.Rd') # Rdiff.Rd from 'tools'
package source
eglist<- list( scrunge=parse_Rd( 'd:/temp/scrunge.Rd'))
tools:::makeLazyLoadDB( eglist, 'd:/temp/ll')
e<- new.env()
lazyLoad( 'd:/temp/ll', e)
a
r.
>
> If there is no way to trigger this bug without using internals, then
> it has not been demonstrated to be a bug in R. It might be one, or
> it might be a bug in your code. Often I'll work on things that are
> demonstrated bugs, but I won't commit several hour
in your code. Often I'll work on things that are demonstrated bugs, but
> I won't commit several hours to debugging your code.
>
> Duncan Murdoch
>
>> Mark Bravington
>>
>>
>> ____________
>> From: Duncan Murdoch [murd...@stats.uwo.ca]
>> Sent: 0
ngton, Mark (CMIS, Hobart)
Cc: r-devel@r-project.org
Subject: Re: [Rd] parse_Rd and/or lazyload problem
On 31/10/2009 10:18 PM, mark.braving...@csiro.au wrote:
Does this happen in R-patched? I've seen similar errors in 2.10.0, but
not in a current build.
Yes, still there in R-patched.
(Stil
tats.uwo.ca]
Sent: 02 November 2009 01:08
To: Bravington, Mark (CMIS, Hobart)
Cc: r-devel@r-project.org
Subject: Re: [Rd] parse_Rd and/or lazyload problem
On 31/10/2009 10:18 PM, mark.braving...@csiro.au wrote:
>> Does this happen in R-patched? I've seen similar errors in 2.10.0, but
&g
o be
something strange going on; my code is very similar to code that lives inside
'tools:::.install_package_Rd_objects'. The problems occur with just-released
R2.10.0 on Windows.
object.size() has problems when working on Rd objects, because it counts
every environment separately, even t
be
>>> something strange going on; my code is very similar to code that lives
>>> inside
>>> 'tools:::.install_package_Rd_objects'. The problems occur with
>>> just-released R2.10.0 on Windows.
>> object.size() has problems when working on R
_
From: Duncan Murdoch [murd...@stats.uwo.ca]
Sent: 31 October 2009 08:59
To: Bravington, Mark (CMIS, Hobart)
Cc: r-devel@r-project.org
Subject: Re: [Rd] parse_Rd and/or lazyload problem
On 30/10/2009 12:50 AM, mark.braving...@csiro.au wrote:
I'm encountering problems when m
e it counts
> every environment separately, even though they may all be references to
> the same one. I haven't looked at your code, but that could be a problem.
>
>
Mark
From: Duncan Murdoch [murd...@stats.uwo.ca]
Sent: 31 October 2009
On 30/10/2009 12:50 AM, mark.braving...@csiro.au wrote:
I'm encountering problems when making lazy-loadable databases of the output
from 'parse_Rd'. The lazy-load database is of seemingly limitless size when I
try to reload it... Admittedly I am using functions that I'm not really
supposed to
I'm encountering problems when making lazy-loadable databases of the output
from 'parse_Rd'. The lazy-load database is of seemingly limitless size when I
try to reload it... Admittedly I am using functions that I'm not really
supposed to use, which is why this isn't a bug report, but there does
14 matches
Mail list logo
