On 05/03/2017 12:04 PM, Hervé Pagès wrote:
Not sure why the performance penalty of nonstandard evaluation would
be more of a concern here than for something like switch().
which is actually a primitive. So it seems that there is at least
another way to go than 'dots <-
Not sure why the performance penalty of nonstandard evaluation would
be more of a concern here than for something like switch().
If that can't/won't be fixed, what about fixing the man page so it's
in sync with the current behavior?
Thanks,
H.
On 05/03/2017 02:26 AM, peter dalgaard wrote:
The
Hi,
Ahh, ok. What I meant was that the "master" branch in
Bioconductor-mirror is not up to date with bioc-devel. I could see
that aCGH did have a release-3.5 branch, but that the "master" branch
wasn't updated. You can see something similar for
> On 3 May 2017, at 19:51, Martin Morgan wrote:
>
> On 05/03/2017 01:10 PM, Leonardo Collado Torres wrote:
>> Hi,
>>
>> I don't think that any of the Bioconductor-mirror repos have been
>> updated to match the current bioc-devel branch. For example, look at
>>
On 05/03/2017 01:10 PM, Leonardo Collado Torres wrote:
Hi,
I don't think that any of the Bioconductor-mirror repos have been
updated to match the current bioc-devel branch. For example, look at
https://github.com/Bioconductor-mirror/aCGH/blob/master/DESCRIPTION#L4
which is one of the first
Now fixed in R-devel revision 72650.
Duncan Murdoch
On 02/05/2017 4:11 AM, Duncan Murdoch wrote:
On 01/05/2017 8:49 PM, Jack Kelley wrote:
Thanks for looking into this.
A few notes regarding all the UTF encodings on Windows 10 ...
This all stems from the ancient bad decision by Microsoft
Hi,
I don't think that any of the Bioconductor-mirror repos have been
updated to match the current bioc-devel branch. For example, look at
https://github.com/Bioconductor-mirror/aCGH/blob/master/DESCRIPTION#L4
which is one of the first packages by alphabetical order. My guess is
that they are
Package developers list:
I recently added an 'as.mcmc.list' method for objects in one of my packages.
Now, in doing an --as-cran check, I get this message:
* checking S3 generic/method consistency ... NOTE
Found the following apparent S3 methods exported but not registered:
as.mcmc.list
See
Ximin Luo:
> [..]
>
> I've attached a patch (applies to both 3.3.3 and 3.4) that fixes this issue;
> however I know it's not perfect and would welcome feedback on how to make it
> acceptable to the R project.
>
Hi all, attached is an updated version of the patch.
We've tested this on our