Hi,
I have a R script file with Persian letters in it defined as a variable:
#' @export
letters_fa <- c('الف','ب','پ','ت','ث','ج','چ','ح','خ','ر','ز','د')
I have specified the encoding field in my DESCRIPTION file of my package.
...
Encoding: UTF-8
...
I also included Sys.setlocale(locale="Per
We do not have the 'at a minimum' information requested by the posting
guide, and I cannot reproduce anything like this on a Unix-alike. Both
file.edit and edit.default call the same underlying C code, and that
single-quotes the 'editor' argument to allow for spaces in its path/name
so I would
Thanks for the great discussion everyone!
Hadley
On Sat, Aug 25, 2018 at 8:26 AM Hadley Wickham wrote:
>
> Hi all,
>
> Would someone mind pointing to me to the inspiration for the use of
> the L suffix to mean "integer"? This is obviously hard to google for,
> and the R language definition
> (htt
>> conflicted applies a few heuristics to minimise false positives (at the
>> cost of introducing a few false negatives). The overarching goal is to
>> ensure that code behaves identically regardless of the order in which
>> packages are attached.
>>
>> - A number of packages provide a function t
Dear Tomas, thank you very much. I installed r-devel r75201 and tested.
The machine with 88 cores has NUMA disabled. It therefore has 2 processor
groups with 64 and 24 processors each.
require(parallel)
detectCores()
# [1] 88
This is great!
Then I went on to test with a simple 'foreach()' loop
