Given a char `c' which should be the start byte of a utf8 character,
the utf8clen function returns the byte length of the utf8 character.
Before this patch, the utf8clen function would return either:
* 1 if `c' was an ascii character or a utf8 continuation byte
* An int in the range [2, 6
Hi,
the function outer can not apply a constant function as in the last line of the
following example:
> xg <- 1:4
> yg <- 1:4
> fxyg <- outer(xg, yg, function(x,y) x*y)
> fconstg <- outer(xg, yg, function(x,y) 1.0)
Error in outer(xg, yg, function(x, y) 1) :
dims [product 16] do not match the
On 19/03/2017 2:31 AM, Sahil Kang wrote:
Given a char `c' which should be the start byte of a utf8 character,
the utf8clen function returns the byte length of the utf8 character.
Before this patch, the utf8clen function would return either:
* 1 if `c' was an ascii character or a utf8 contin
Michael Lawrence (as last in long series of posters)...
> Yes, it would bind the language object to the environment, like an
> R-level promise (but "promise" of course refers specifically to just
> _lazy_ evaluation).
>
> For the uqs() thing, expanding calls like that is somewhat orthogonal
> to
On Mon, Mar 20, 2017 at 7:36 AM, Radford Neal wrote:
> Michael Lawrence (as last in long series of posters)...
>
>> Yes, it would bind the language object to the environment, like an
>> R-level promise (but "promise" of course refers specifically to just
>> _lazy_ evaluation).
>>
>> For the uqs()
C++ support across different platforms is now very heterogeneous. The standard
is evolving rapidly but there are also platforms in current use that do not
support the recent iterations of the standard. Our goal for R 3.4.0 is to give
as much flexibility as possible. The default compiler is whate
Some of the code that uses utf8clen checks the validity of the utf8
string before making the call.
However, there were some hairy areas where I felt that the new semantics
may cause issues (if not now, then in future changes).
I've attached two patches:
* new_semantics.diff keeps the new se
Hi all,
I try to compile my package kml and I get the message
Warning in read_symbols_from_dll(so,rarch):
this requires 'objdump.exe' to be on the PATH
I check 'Writing R Extensions' but I did not find any reference to this error. Does someone know how
to fix that?
Thank you very much for yo
