From ggrothendieck at gmail.com  Sat Dec 25 00:49:52 2010
From: ggrothendieck at gmail.com (Gabor Grothendieck)
Date: Fri, 24 Dec 2010 18:49:52 -0500
Subject: [Rd] LazyLoad changes the class of objects
In-Reply-To: <Pine.LNX.4.64.0710170759210.12037@nokomis.stat.uiowa.edu>
References: <971536df0710120004k236f017je01153dcf55869dd@mail.gmail.com>
	<Pine.LNX.4.64.0710170759210.12037@nokomis.stat.uiowa.edu>
Message-ID: <AANLkTimEoV6v9bsSj4YQv53c78_GOVzG8Tac1=St0SaV@mail.gmail.com>

On Wed, Oct 17, 2007 at 8:59 AM, Luke Tierney <luke at stat.uiowa.edu> wrote:
> Yes, attributes are not preserved, though why that should matter
> given the frequent strong recommendations in this list against
> using attributes on environments or other reference objects is
> beyond me. More importantly, locking and active bindings are not
> preserved either. ?Will look into fixing this this 2.7.
>

1. The above message from 2007 was about the possibility of fixing the
fact that attributes on top level environments are stripped if
LazyLoad: yes in a package's DESCRIPTION file.   (They are not
stripped if LazyLoad: false so that case works as expected -- its only
the LazyLoad: true case that has this behavior.)  Can this be finally
fixed?

2. There was an R News article at the time that mentioned an
undocumented 25K code size threshold that determined whether LazyLoad
was turned on or off in those cases where LazyLoad was not specified
in the DESCRIPTION file.  Is that still the case?   If not then what
is the default?  Its not mentioned in the R-ext manual.

-- 
Statistics & Software Consulting
GKX Group, GKX Associates Inc.
tel: 1-877-GKX-GROUP
email: ggrothendieck at gmail.com



[Rd] LazyLoad changes the class of objects
Gabor Grothendieck