turns out we RcppLdFlags and LdFlags -- so both exported and documented now

Author: eddelbuettel

ChangeLog

@@ -1,7 +1,7 @@
 2013-10-08  Dirk Eddelbuettel  <edd@debian.org>
 
-	* NAMESPACE: Export LdFlags, not RcppLdFlags
-	* man/LdFlags.Rd: Renamed from RcppLdFlags, and changed
+	* NAMESPACE: Export LdFlags as well as RcppLdFlags
+	* man/RcppLdFlags.Rd: Updated
 
 2013-10-06  John M Chambers  <jmc@r-project.org>
 

NAMESPACE

@@ -26,6 +26,7 @@ export(Module,
        sourceCpp,
        compileAttributes,
        registerPlugin,
+       RcppLdFlags,
        LdFlags,
        demangle,
        sizeof,

inst/NEWS.Rd

@@ -2,7 +2,7 @@
 \title{News for Package 'Rcpp'}
 \newcommand{\cpkg}{\href{http://CRAN.R-project.org/package=#1}{\pkg{#1}}}
 
-\section{Changes in Rcpp version 0.10.5.1 (2013-10-07)}{
+\section{Changes in Rcpp version 0.10.5.2 (2013-10-08)}{
   \itemize{
     \item Changes in Rcpp API:
     \itemize{
@@ -11,15 +11,15 @@
         class, and writes C++ and R files in the package.  Inherited
         classes can be dealt with, but require data type information.
         This approach avoids hand-coding module files.
-
       \item Two missing \code{is<>()} templates for
-      \code{CharacterVector} and \code{CharacterMatrix} have been added,
-      and some tests for \code{is_na()} and \code{is_finite()} have been
-      corrected thanks to Thomas Tse.   
+        \code{CharacterVector} and \code{CharacterMatrix} have been added,
+        and some tests for \code{is_na()} and \code{is_finite()} have been
+        corrected thanks to Thomas Tse.   
     }
     \item Changes in R code:
     \itemize{
-      \item Export linking helper function \code{LdFlags}, not \code{RcppLdFlags}
+      \item Export linking helper function \code{LdFlags} as well as
+        \code{RcppLdFlags}.
     }
   }
 }

man/LdFlags.Rd man/RcppLdFlags.Rdman/LdFlags.Rd renamed to man/RcppLdFlags.Rd

@@ -1,17 +1,19 @@
 \name{LdFlags}
 \alias{LdFlags}
+\alias{RcppLdFlags}
 \title{Provide Rcpp Linker Flags}
 \description{
-  \code{LdFlags} returns the required flags and options for the the
-  system linker. This allows portable use of \pkg{Rcpp} as package
-  location as well as operating-system specific details are abstracted
-  away behind the interface of this function.
+  \code{LdFlags} and \code{RcppLdFlags} return the required flags and
+  options for the the system linker. This allows portable use of
+  \pkg{Rcpp} as package location as well as operating-system specific
+  details are abstracted away behind the interface of this function.
 
-  It is commonly called from the files \code{Makevars} (or
+  \code{LdFlags} is commonly called from the files \code{Makevars} (or
   \code{Makevars.win}) rather than in an interactive session.
 }
 \usage{
 LdFlags(static=staticLinking())
+RcppLdFlags(static=staticLinking())
 }
 \arguments{
   \item{static}{A boolean determining use of static (as opposed to
@@ -24,7 +26,7 @@ LdFlags(static=staticLinking())
   create a library based on \pkg{Rcpp}.
 }
 \details{
-  This function is not meant to used interactively, and is intended
+  Thee functions are not meant to used interactively, and are intended
   solely for use by the build tools.
 }
 \references{