Dear Dirk,
Thanks a lot for your detailed explanation. This is indeed the solution that I
have found to work nicely, and indeed keeps the code equally tidy.
In fact, I am finding that using :: to access exported objects instead of :::
to access any object in the data package even helps me organi
On 2 May 2021 at 15:00, Ayala Hernandez, Rafael wrote:
| Thanks a lot for your clarifications. Both of your explanations make sense.
Indeed, I would rather not have any other packages depend on the data package,
at least not for the time being, in case I find good reasons to make
modifications
Dear Dirk and Duncan,
Thanks a lot for your clarifications. Both of your explanations make sense.
Indeed, I would rather not have any other packages depend on the data package,
at least not for the time being, in case I find good reasons to make
modifications in the data package.
But it makes
On 02/05/2021 8:44 a.m., Dirk Eddelbuettel wrote:
On 2 May 2021 at 10:12, Ayala Hernandez, Rafael wrote:
| Following Dirk's suggestion below, I have recently added a data package as a
drat repository for my asteRisk package, placing it under Suggests in the main
package.
| In order to keep the
On 2 May 2021 at 10:12, Ayala Hernandez, Rafael wrote:
| Following Dirk's suggestion below, I have recently added a data package as a
drat repository for my asteRisk package, placing it under Suggests in the main
package.
| In order to keep the code tidy and know exactly when I’m accessing the
Dear All,
Following Dirk's suggestion below, I have recently added a data package as a
drat repository for my asteRisk package, placing it under Suggests in the main
package.
In order to keep the code tidy and know exactly when I’m accessing the data in
the data package, I access all the data i
