Dear all,
I initially ran into this problem while rebuilding a package dependent on
nleqslv. I got the following error:
Error in match.arg(global) : 'arg' must be of length 1
This didn't occur in previous versions of nleqslv, but did in the current
one (2.4). I think I pinned the problem down to
This is one of the perils of non-standard evaluation - functions are
no longer referentially transparent.
Hadley
On Mon, Aug 25, 2014 at 9:27 AM, Joris Meys wrote:
> Dear all,
>
> I initially ran into this problem while rebuilding a package dependent on
> nleqslv. I got the following error:
>
>
More specifically, you're satisifying and not satisfying
if (identical(arg, choices))
return(arg[1L])
within the definition of match.args for x, and global, respectively.
arg is what is passed to the function (outer default) but choices isn't
specified so match.args uses nonstandard
> peter dalgaard
> on Thu, 21 Aug 2014 16:11:38 +0200 writes:
> On 21 Aug 2014, at 15:47 , Duncan Murdoch
> wrote:
>> On 21/08/2014 9:26 AM, Richard Cotton wrote:
>>> If you set the names in a list, some cat-style
>>> processing seems to happen. For example, bac
On 25 Aug 2014, at 16:27 , Joris Meys wrote:
> Dear all,
>
> I initially ran into this problem while rebuilding a package dependent on
> nleqslv. I got the following error:
>
> Error in match.arg(global) : 'arg' must be of length 1
>
> This didn't occur in previous versions of nleqslv, but di
On 25-08-2014, at 16:27, Joris Meys wrote:
> Dear all,
>
> I initially ran into this problem while rebuilding a package dependent on
> nleqslv. I got the following error:
>
> Error in match.arg(global) : 'arg' must be of length 1
>
> This didn't occur in previous versions of nleqslv, but did
I’m preparing a package (fastR) for submission to CRAN, but the vignette index
keeps going AWOL, or at least R CMD check —as-cran thinks so. I’ve tried
several things and gave myself the weekend to think of other things, but I
can’t figure it out. Perhaps someone on the list can lend a hand.
H
Hi Randall,
I notice that, in your .Rbuildignore, you have the entry:
^build$
and I suspect this is the culprit (having being bitten by a similar
problem before). Some part of the R build / install process creates /
uses that directory, but having it excluded in .Rbuildignore will
cause you
Indeed! That should say “builds” rather than “build”. It is the directory
where I keep old tar balls from the package. I see builds is there as well.
Somewhere along the way I must have stuttered while editing and introduced the
problematic line. I’ve removed it and things are back to sanit
