Thanks, Mark - I'm taking up your invitation to forward your message
to the list just because it gives us some valuable data on (1) how
long the behavior has been around, and (2) how many other people
(don't) understand the behavior, and (3) how we might fix or work
around it.
I notice some other
Thanks John,
As the problem can be reproduced, I would like to submit this as a bug
report. But I think someone will have to add me to Bugzilla first.
Given the few responses, I am not expecting that this will get a high
priority though...
Jon
On 12/7/2016 2:59 PM, Fox, John wrote:
Dear Mar
I have narrowed down the problem.
The error
Error : 'AminoAcids' is not an exported object from 'namespace:bibliospec'
Error : unable to load R code in package 'bibliospec'
occurs only if I try to access the data using bibliospec::AminoAcids
within the initialize method of an R reference class.
I
You can define the data in the R directory. You can keep it all in a *.R
file
by wrapping the text of the *.csv file in quotes and using
read.table(text="quoted stuff"), as in:
theData <- read.csv(header=TRUE, text="
English,Digit
One,1
Two,2
Three,3")
N <- nrow(theData)
You need to make sure 't
Witold,
Are you using the sys data approach to actually put your data into your
package's namespace? From ?data (Good practices section)
Use of ‘data’ within a function without an ‘envir’ argument has
the almost always undesirable side-effect of putting an object in
the user's workspa
Hi Frederik
Goodo, glad you found mvbutils::mvb.parent.frame useful. I had forgotten that
it's in mvbutils rather than debug package. This all dates back about 15
years...
To be fair, I don't think R's behaviour with duplicated-but-aliased frames in
the call stack is a "bug"--- everything norm
