On Fri, Oct 31, 2014 at 7:34 PM, Gábor Csárdi <csardi.ga...@gmail.com> wrote: > Dear All, > > I am trying to do the following, and could use some hints. > > Suppose I have a package called pkgA. pkgA exposes an API that > includes setting some options, e.g. pkgA works with color palettes, > and the user of the package can define new palettes. pkgA provides an > API to manipulate these palettes, including defining them. > > pkgA is intended to be used in other packages, e.g. in pkgB1 and > pkgB2. Now suppose pkgB1 and pkgB2 both set new palettes using pkgA. > They might set palettes with the same name, of course, they do not > know about each other. > > My question is, is there a straightforward way to implement pkgA's > API, such that pkgB1 and pkgB2 do not interfere? In other words, if > pkgB1 and pkgB2 both define a palette 'foo', but they define it > differently, each should see her own version of it. > > I guess this requires that I put something (a function?) in both > pkgB1's and pkgB2's package namespace. As I see it, this can only > happen when pkgA's API is called from pkgB1 (and pkgB2). > > So at this time I could just walk up the call tree and put the palette > definition in the first environment that is not pkgA's. This looks > somewhat messy, and I am probably missing some caveats. > > Is there a better way? I have a feeling that this is already supported > somehow, I just can't find out how. >
Try the settings package. ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
