similar to: problems with RdMacros in file DESCRIPTION

Another, perhaps slightly off the wall reframing of the 3-package possibility: Have packages B, a, and UserFacingA, as follows *a* contains all the functionality in your A package that *does not depend on B* *B* *imports from* *a* and is essentially unchanged *UserFacingA* *Depends* on *a* and *imports from* *B*, it implements all functionality from your package A that *does depend on* *B*, and

A third possibility, which I use in my gtools and gdata packages, is to use soft-links to create a copy of the relevant functions from one package in the other. I make sure these functions are *not* exported, so no conflicts are created, and the use of soft-links mean the code never gets out of sync. -Greg -- Change your thoughts and you change the world. --Dr. Norman Vincent Peale > On

In that scenario, I would expect that QCA would suggest Venn and Venn would suggest QCA. Then there's no circular dependency problem. Hadley On Fri, Apr 8, 2016 at 6:59 AM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Mark, > > Uhm... sometimes this is not always possible. > For example I have a package QCA which produces truth tables (all > combinations of

Thanks all, I don't know either (for the moment). It's all in the design phase still. Generally, I would also like to keep specific functions in specific packages, if at all possible. On Fri, Apr 8, 2016 at 3:03 PM, Mark van der Loo <mark.vanderloo at gmail.com> wrote: > Well, I'm not saying that Dmitri _should_ do it. I merely mention it as an > option that I think is

Well, I'm not saying that Dmitri _should_ do it. I merely mention it as an option that I think is worth thinking about -- it is easy to overlook the obvious :-). Since we have no further info on the package's structure we can't be sure.. Op vr 8 apr. 2016 om 13:59 schreef Adrian Du?a <dusa.adrian at unibuc.ro>: > Hi Mark, > > Uhm... sometimes this is not always

Hi Mark, Uhm... sometimes this is not always possible. For example I have a package QCA which produces truth tables (all combinations of presence / absence of causal conditions), and it uses the venn package to draw a Venn diagram. It is debatable if one should assimilate the "venn" package into the QCA package (other people might want Venn diagrams but not necessarily the other QCA

Hi Thierry, Thanks for that, the trouble is functions are package specific so moving from one package to another could be a solution, but I would rather save that as a last resort. As mentioned, creating a package C with all the common functions could also be an option, but this strategy quickly inflates the number of packages on CRAN. If no other option is possible, that could be the way but I

>>>>> Adrian Du?a <dusa.adrian at unibuc.ro> >>>>> on Tue, 13 Mar 2018 09:17:08 +0200 writes: > On Mon, Mar 12, 2018 at 2:18 PM, Martin Maechler <maechler at stat.math.ethz.ch> > wrote: >> [...] >> Is that so? Not according to my reading of the 'Writing R >> Extensions' manual, nor according to

Adrian, That is indeed a specialized need albeit not necessarily one that cannot be done by requiring an alternate way of typing a formula that avoids being something the parser sees as needed to do at that level. In this case, my other questions become moot as I assume the global assignment operator and somethings like assign(?xyz?, 5) will not be in the way. What I was wondering about is

On Mon, Mar 12, 2018 at 2:18 PM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > [...] > Is that so? Not according to my reading of the 'Writing R > Extensions' manual, nor according to what I have been doing in > all of my packages for ca. 2 years: > > The rule I have in my mind is > > 1) NAMESPACE Import(s|From) \ >

At the risk of stating the over-obvious: there's also the option of creating just a single package containing all functions. None of the functions that create the interdependencies need to be exported that way. Btw, his question is probably better at home at the r-package-devel list. Best, M On Thu, Apr 7, 2016, 22:24 Dmitri Popavenko <dmitri.popavenko at gmail.com> wrote: >

> but this strategy quickly inflates the number of packages on CRAN. CRAN contains 8210 packages today, so I would not worry about adding an extra one. Also, I think several small packages are preferable to one large one because attaching a big one just to get the one or two functions you want is also a waste. Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Apr 7, 2016 at 1:22 PM,

Thanks! On 05 Apr 2016, at 16:07, Thierry Onkelinx <thierry.onkelinx at inbo.be<mailto:thierry.onkelinx at inbo.be>> wrote: You could use something like this x <- abs(0.95 - 1) treshold <- 0.05 x < treshold | abs(x - treshold) < 1e-6 ir. Thierry Onkelinx Instituut voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie &

I would also be interested in that. For me, this is interesting for my QCA package, over which Dmitri and I have exchanged a couple of messages. The "<-" operator is used to denote necessity, and the "->" is used for sufficiency. Users often make use of Boolean expressions such as A*B + C -> Y (to calculate if the expression A*B + C is sufficient for the outcome Y)

Dear Dmitri, If it's only a small number of functions then move them the relevant functions for A to B so that B works without A. Then Import these functions from B in A. Hence A depends on B but B is independent of A. It is requires to move a lot of functions than you better create a package C with all the common functions. Then A and B import those functions from C. Best regards, ir.

You could use something like this x <- abs(0.95 - 1) treshold <- 0.05 x < treshold | abs(x - treshold) < 1e-6 ir. Thierry Onkelinx Instituut voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team Biometrics & Quality Assurance Kliniekstraat 25 1070 Anderlecht Belgium To call in the statistician after the experiment is

Dear r-devel, I am trying to automatically check if two successive versions of a package have the same results (i.e. code not broken), by parsing the example sections for each function against a previously tested version. While trying to replicate the code from example(), I am facing an error related with te "index.search" function (line 7 in the example() code). This is the code I am

Adrian, I am not on the CRAN or R-core teams, so the following is my own view, but... > library(QCA) > > Users are encouraged to cite this package as: > > Dusa, Adrian (2015). QCA: Qualitative Comparative Analysis. R Package > Version 1.2-0, > URL: http://cran.r-project.org/package=QCA > > This is just an encouragement, not a requirement, and the official citation

%=>% would have precendence ('order of operations') problems also. A + B %=>% C is equivalent to A + ( B %=>% C) and I don't think that is what you want. as.list(quote(A + B %=>% C)) shows the first branch in the parse tree. The following function, str.language, shows the entire parse tree, as in > str.language(quote(A + B %=>% C)) `quote(A + B %=>%

On Tue, Oct 6, 2015 at 3:06 AM, Simon Urbanek <simon.urbanek at r-project.org> wrote: > > [...] > > To clarify, legally, you can fork a standard GPL package and make any > changes you want, including changing authors fields etc. If you don't own > copyright for the entire work then you cannot change the license without > consent from the other copyright holders,