[Rd] Patch for R-exts.texi
Attached is a patch for R-exts.texi against r72880.
Here are some of the changes I made:
- Fix a broken link:
https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/Introduction/Introduction.html
->
https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html
- Changed a few http to https (and checked that the connections are
indeed secure, as judged by Chromium and Firefox).
- A couple of grammar fixes and "sounds more natural to me" changes.
- "x84_64" -> x86_64
- One change of "which" -> "that"
- The link to Luke's uiowa.edu page involves two changes, removing the
duplicate URL and changing the protocol to https.
Thanks for your time,
Scott
--
Scott Kostyshak
Assistant Professor of Economics
University of Florida
https://people.clas.ufl.edu/skostyshak/
Index: doc/manual/R-exts.texi
===
--- doc/manual/R-exts.texi (revision 72880)
+++ doc/manual/R-exts.texi (working copy)
@@ -1457,7 +1457,7 @@
@noindent
then download the sources from
-@uref{http://sourceforge.net/@/projects/@/tcllib/@/files/@/BWidget/} and
+@uref{https://sourceforge.net/@/projects/@/tcllib/@/files/@/BWidget/} and
at the command line run something like
@example
@@ -1494,7 +1494,7 @@
@noindent
and not a version starting
-@samp{http://cran.r-project.org/web/packages/@var{pkgname}}.
+@samp{https://cran.r-project.org/web/packages/@var{pkgname}}.
@node Configure and cleanup, Checking and building packages, Package
structure, Creating R packages
@section Configure and cleanup
@@ -2117,7 +2117,7 @@
word, so computations done on OpenMP threads will not make use of
extended-precision arithmetic which is the default for the main process.
@c mingw64-public, 2015-02-02.
-@c
http://stackoverflow.com/questions/2553725/is-the-fpu-control-word-setting-per-thread-or-per-process
+@c
https://stackoverflow.com/questions/2553725/is-the-fpu-control-word-setting-per-thread-or-per-process
Calling any of the @R{} API from threaded code is `for experts only':
they will need to read the source code to determine if it is
@@ -7645,7 +7645,7 @@
which is a GUI version), @command{Shark} (in version of @code{Xcode}
up to those for Snow Leopard), and @command{Instruments} (part of
@code{Xcode}, see
-@uref{https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/Introduction/Introduction.html}).
+@uref{https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html}).
@node Debugging, System and foreign language interfaces, Tidying and profiling
R code, Top
@@ -8295,8 +8295,8 @@
to be installed separately, and for checking C++ you may also need
@pkg{libubsan}.} of @command{gcc} and @command{clang} on common Linux
and macOS platforms. See
-@uref{http://clang.llvm.org/@/docs/@/UsersManual.html#controlling-code-generation},
-@uref{http://clang.llvm.org/@/docs/@/AddressSanitizer.html} and
+@uref{https://clang.llvm.org/@/docs/@/UsersManual.html#controlling-code-generation},
+@uref{https://clang.llvm.org/@/docs/@/AddressSanitizer.html} and
@uref{https://code.google.com/@/p/@/address-sanitizer/}.
More thorough checks of C++ code are done if the C++ library has been
@@ -8455,7 +8455,7 @@
Finer control of what is checked can be achieved by other options: for
@command{clang} see
-@uref{http://clang.llvm.org/@/docs/@/UsersManual.html#controlling-code-generation}.@footnote{or
+@uref{https://clang.llvm.org/@/docs/@/UsersManual.html#controlling-code-generation}.@footnote{or
the user manual for your version of @command{clang}, e.g.@: (the paths
have differed for some versions)
@uref{http://llvm.org/@/releases/@/4.0.0/@/tools/@/clang/@/docs/@/UsersManual.html}.}
@@ -8560,13 +8560,13 @@
Recent versions of @command{clang} on @cputype{x86_64} Linux have
`ThreadSanitizer' (@uref{https://code.google.com/@/p/@/thread-sanitizer/}),
a `data race detector for C/C++ programs', and `MemorySanitizer'
-(@uref{http://clang.llvm.org/@/docs/@/MemorySanitizer.html},
+(@uref{https://clang.llvm.org/@/docs/@/MemorySanitizer.html},
@uref{https://code.google.com/@/p/@/memory-sanitizer/@/wiki/@/MemorySanitizer})
for the detection of uninitialized memory. Both are based on and
provide similar functionality to tools in @command{valgrind}.
@command{clang} has a `Static Analyser' which can be run on the source
-files during compilation: see @uref{http://clang-analyzer.llvm.org/}.
+files during compilation: see @uref{https://clang-analyzer.llvm.org/}.
@node Using `Dr. Memory', Fortran array bounds checking, Other analyses with
`clang', Checking memory access
@subsection Using `Dr. Memory'
@@ -9429,7 +9429,7 @@
@uref{https://www.r-project.org/@/doc/@/Rnews/Rnews_2001-3.pdf}).
Once routines are registered, they can be referred to as @R{} objects if
-th
Re: [Rd] Are you considering the possibility of partnership?
Plese stop this. Best, Uwe Ligges On 03.07.2017 11:29, Keira Cohen wrote: Hi, I've sent you partnership offer via e-mail several days ago. Did you receive it? Are you interested in placing ads on your site? Best regards, Keira On Fri, Jun 30, 2017 at 11:10 AM, Keira Cohen wrote: Hi, did you receive my mail about ad placements? If so it would be great to get a feedback from you. Best regards, Keira On Wed, Jun 28, 2017 at 11:54 AM, Keira Cohen wrote: Hi, I'm software developer and I think it might be great to advertise my software on your web site. If you are interested in partnership please contact me at any time. Best regards, Keira [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Are you considering the possibility of partnership?
On 2017-07-03 2:02 PM, Uwe Ligges wrote: Plese stop this. People who reply to spammers only invite more spam. The only way I know to defeat them is to get software to block them. The anti-spam software I have is not great but is better than nothing. Spencer Best, Uwe Ligges On 03.07.2017 11:29, Keira Cohen wrote: Hi, I've sent you partnership offer via e-mail several days ago. Did you receive it? Are you interested in placing ads on your site? Best regards, Keira On Fri, Jun 30, 2017 at 11:10 AM, Keira Cohen wrote: Hi, did you receive my mail about ad placements? If so it would be great to get a feedback from you. Best regards, Keira On Wed, Jun 28, 2017 at 11:54 AM, Keira Cohen wrote: Hi, I'm software developer and I think it might be great to advertise my software on your web site. If you are interested in partnership please contact me at any time. Best regards, Keira [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Are you considering the possibility of partnership?
Hi All, Just an FYI, that the sender's e-mail was set up last week to auto-discard for R-Devel and their reply below to R-Devel was filtered in that manner. Unfortunately, it would seem that they also targeted some other specific accounts as well. As Spencer notes, I would add their e-mail address to any spam filters folks may be using. Regards, Marc > On Jul 3, 2017, at 7:07 AM, Spencer Graves > wrote: > > > > On 2017-07-03 2:02 PM, Uwe Ligges wrote: >> Plese stop this. > > > People who reply to spammers only invite more spam. The only way I know > to defeat them is to get software to block them. The anti-spam software I > have is not great but is better than nothing. > > > Spencer > >> >> Best, >> Uwe Ligges >> >> >> >> On 03.07.2017 11:29, Keira Cohen wrote: >>> Hi, >>> >>> I've sent you partnership offer via e-mail several days ago. Did you >>> receive it? Are you interested in placing ads on your site? >>> >>> >>> Best regards, >>> Keira >>> >>> On Fri, Jun 30, 2017 at 11:10 AM, Keira Cohen wrote: >>> Hi, did you receive my mail about ad placements? If so it would be great to get a feedback from you. Best regards, Keira On Wed, Jun 28, 2017 at 11:54 AM, Keira Cohen wrote: > Hi, > I'm software developer and I think it might be great to advertise my > software on your web site. If you are interested in partnership please > contact me at any time. > > Best regards, > Keira > >>> >>>[[alternative HTML version deleted]] >>> >> >> __ >> R-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel > > __ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] The ByteCompile & LazyLoading fields
Hi, In the DESCRIPTION file the ByteCompile and LazyLoading arguments appear to accept any value. >From the manual the field should be a "logical field". However, authors interpret this in a variety of ways: unique(tools::CRAN_package_db()$ByteCompile) # [1] NA "TRUE" "yes" "true" "Yes" "no" # unique(tools::CRAN_package_db()$LazyData) # [1] NA "true" "TRUE" "yes" "no" "false" # [7] "True" "Yes""FALSE" "YES" "LazyData: true" "NA" # [13] "No" I presume that all non NA are treated as TRUE. This observation applies to other logical fields in the DESCRIPTION file. Colin [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] R_LIBS_USER on Ubuntu 16.04
Dear all,
the recent update to R-3.4.1 kind of screwed the path to the libraries
installed on a user basis.
The previous version of the file /etc/R/Renviron had the following line
activated:
R_LIBS_USER=${R_LIBS_USER-'~/R/x86_64-pc-linux-gnu-library/3.4'}
This one is commented in the current one which means that the path to the
libraries installed previously is not found. I never touched this file before.
Was that on purpose or did that happen accidentally?
Cheers,
STefan
signature.asc
Description: This is a digitally signed message part.
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R_LIBS_USER on Ubuntu 16.04
Hi Stefan,
This is a packaging issue, not a change in the R source code. Further,
it has already been discussed on R-sig-debian -- see
https://stat.ethz.ch/pipermail/r-sig-debian/2017-July/thread.html
Best,
Ista
On Mon, Jul 3, 2017 at 9:35 AM, Stefan Lüdtke wrote:
> Dear all,
>
> the recent update to R-3.4.1 kind of screwed the path to the libraries
> installed on a user basis.
>
> The previous version of the file /etc/R/Renviron had the following line
> activated:
>
> R_LIBS_USER=${R_LIBS_USER-'~/R/x86_64-pc-linux-gnu-library/3.4'}
>
> This one is commented in the current one which means that the path to the
> libraries installed previously is not found. I never touched this file before.
>
> Was that on purpose or did that happen accidentally?
>
> Cheers,
>
> STefan
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] R_LIBS_USER on Ubuntu 16.04
On 3 July 2017 at 15:35, Stefan Lüdtke wrote:
| the recent update to R-3.4.1 kind of screwed the path to the libraries
| installed on a user basis.
|
| The previous version of the file /etc/R/Renviron had the following line
| activated:
|
| R_LIBS_USER=${R_LIBS_USER-'~/R/x86_64-pc-linux-gnu-library/3.4'}
|
| This one is commented in the current one which means that the path to the
| libraries installed previously is not found. I never touched this file
before.
|
| Was that on purpose or did that happen accidentally?
i) Wrong venue. Discussion of this should be on r-sig-debian.
ii) On purpose. I have explained the rationale there (ie r-sig-debian) as
well as this Debian bug report: https://bugs.debian.org/866768
iii) Easiest fix: Remove _one_ character, the '#' on line 43 of file
/etc/R/Renviron
iv) "Correct" fix is the determine a use policy for directory
/usr/local/lib/R/site-library -- at work several of us are in a shared
group and you can use 'staff' or 'adm'. On my laptop I just give the
directory my own group.
Dirk, at DSC preceding useR! 2017
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
