Displaying 5 results from an estimated 5 matches for "cboundscheck".
Did you mean:
boundscheck
Control statements with condition with greater than one should give error (not just warning) [PATCH]
2017 Mar 03
2
Control statements with condition with greater than one should give error (not just warning) [PATCH]
...item{\code{check.condition}:}{logical, defaulting to \code{FALSE}. If
+ \code{TRUE}, an error is produced whenever the condition to an
+ \code{if} or a \code{while} control statement is of length greater
+ than one. If \code{FALSE}, a \link{warning} is produced.}
+
\item{\code{CBoundsCheck}:}{logical, controlling whether
\code{\link{.C}} and \code{\link{.Fortran}} make copies to check for
array over-runs on the atomic vector arguments.
@@ -445,6 +450,7 @@
\tabular{ll}{
\code{add.smooth} \tab \code{TRUE}\cr
\code{check.bounds} \tab \code{FALSE}\cr
+ \code...
Control statements with condition with greater than one should give error (not just warning) [PATCH]
2017 Mar 03
0
Control statements with condition with greater than one should give error (not just warning) [PATCH]
...efaulting to \code{FALSE}. If
> + \code{TRUE}, an error is produced whenever the condition to an
> + \code{if} or a \code{while} control statement is of length greater
> + than one. If \code{FALSE}, a \link{warning} is produced.}
> +
> \item{\code{CBoundsCheck}:}{logical, controlling whether
> \code{\link{.C}} and \code{\link{.Fortran}} make copies to check for
> array over-runs on the atomic vector arguments.
> @@ -445,6 +450,7 @@
> \tabular{ll}{
> \code{add.smooth} \tab \code{TRUE}\cr
> \code{check.bounds} \tab...
Control statements with condition with greater than one should give error (not just warning) [PATCH]
2017 Mar 03
2
Control statements with condition with greater than one should give error (not just warning) [PATCH]
.... If
> > + \code{TRUE}, an error is produced whenever the condition to an
> > + \code{if} or a \code{while} control statement is of length greater
> > + than one. If \code{FALSE}, a \link{warning} is produced.}
> > +
> > \item{\code{CBoundsCheck}:}{logical, controlling whether
> > \code{\link{.C}} and \code{\link{.Fortran}} make copies to check for
> > array over-runs on the atomic vector arguments.
> > @@ -445,6 +450,7 @@
> > \tabular{ll}{
> > \code{add.smooth} \tab \code{TRUE}\cr
>...
2013 Apr 03
0
R 3.0.0 is released
...sly they were sometimes taken as transparent, sometimes
mapped into the current palette and sometimes an error.
NEW FEATURES:
o identical() has a new argument, ignore.environment, used when
comparing functions (with default FALSE as before).
o There is a new option, options(CBoundsCheck=), which controls how
.C() and .Fortran() pass arguments to compiled code. If true
(which can be enabled by setting the environment variable
R_C_BOUNDS_CHECK to yes), raw, integer, double and complex
arguments are always copied, and checked for writing off either
end...
2013 Apr 03
0
R 3.0.0 is released
...sly they were sometimes taken as transparent, sometimes
mapped into the current palette and sometimes an error.
NEW FEATURES:
o identical() has a new argument, ignore.environment, used when
comparing functions (with default FALSE as before).
o There is a new option, options(CBoundsCheck=), which controls how
.C() and .Fortran() pass arguments to compiled code. If true
(which can be enabled by setting the environment variable
R_C_BOUNDS_CHECK to yes), raw, integer, double and complex
arguments are always copied, and checked for writing off either
end...