Revision 69c8d344d69fc70f001c8b631223f200452ca0b8 authored by Paul Gilbert on 28 November 2011, 11:59:58 UTC, committed by cran-robot on 28 November 2011, 11:59:58 UTC
1 parent 83ee9d6
DSEflags.Rd
\name{DSEflags}
\alias{.DSEflags}
\title{Flags to Indicate Use of Compiled Code}
\description{
Determines if compiled code should be used or not.
}
\usage{
.DSEflags(new)
}
\arguments{
\item{new}{A list which must have elements COMPILED and DUP.}
}
\details{
Setting flags with this function is primarily for debugging. It should not
normally be needed by users. If called with not arguments,
\code{.DSEflags()} returns the current setting.
Several \pkg{dse} functions which call compiled fortran or C code will use
the equivalent S/R version if the \code{.DSEflags()$COMPILED} returns
\code{FALSE}. \code{.DSEflags()$DUP} is passed to
fortran calls and controls whether R duplicates arguments passed
to the fortran code. The safe setting is \code{TRUE}. Setting \code{FALSE}
saves some memory but does not seem to give much speed gain.
}
\section{Side Effects}{
The flag settings affect whether and how compiled fortran or C code is
called.
}
\examples{
.DSEflags(list(COMPILED=TRUE, DUP=TRUE))
.DSEflags()$COMPILED
}
\concept{DSE}
\keyword{programming}
Computing file changes ...