Hi Peter,
On 11-12-14 08:19 AM, peter dalgaard wrote:
On Dec 14, 2011, at 16:19 , John C Nash wrote:
Following this thread, I wondered why nobody tried cumsum to see where the
integer
overflow occurs. On the shorter xx vector in the little script below I get a
message:
Warning message:
In
On Wed, Dec 14, 2011 at 9:54 PM, Ni Wang wrote:
> hi, r developers, I am now working on a R function/package to handling
> online request with username and token/password.
>
> For security reasons, it's not so safe to store the username & token in
> persistent variables, since they'll be saved to
hi, r developers, I am now working on a R function/package to handling
online request with username and token/password.
For security reasons, it's not so safe to store the username & token in
persistent variables, since they'll be saved to disk when
users save their workspace. Is there a secure wa
On Dec 14, 2011, at 19:43 , RogerP wrote:
>> I used the --disable-nls and --with-included-gettext options. I also
> downloaded the more >up-to-date cairo package.
>
>> BTW, is there a program I can run to test my iconv binary? I think that
> would rule out any >problem with the compilation
On 14.12.2011 22:16, John C Nash wrote:
I agree that where the overflow occurs is not critical (one can go back to
cumsum and find
out). I am assuming that Uwe still wants to know there has been an overflow at
some point
i.e., a warning.
Yes, sure.
Uwe
This could become more "interestin
I agree that where the overflow occurs is not critical (one can go back to
cumsum and find
out). I am assuming that Uwe still wants to know there has been an overflow at
some point
i.e., a warning. This could become more "interesting" as parallel computation
causes
different summation orderings
On 14.12.2011 17:19, peter dalgaard wrote:
On Dec 14, 2011, at 16:19 , John C Nash wrote:
Following this thread, I wondered why nobody tried cumsum to see where the
integer
overflow occurs. On the shorter xx vector in the little script below I get a
message:
Warning message:
Integer over
>I used the --disable-nls and --with-included-gettext options. I also
downloaded the more >up-to-date cairo package.
>BTW, is there a program I can run to test my iconv binary? I think that
would rule out any >problem with the compilation.
>Thanks for you suggestions and for any future hel
On Dec 14, 2011, at 16:19 , John C Nash wrote:
>
> Following this thread, I wondered why nobody tried cumsum to see where the
> integer
> overflow occurs. On the shorter xx vector in the little script below I get a
> message:
>
> Warning message:
> Integer overflow in 'cumsum'; use 'cumsum(as
On Wed, Dec 14, 2011 at 8:15 AM, RogerP wrote:
> For some reason when I click on reply and sign-in - the message I'm replying
> to is not carried forward. As you requested that include your message I
> copied and pasted it from my email.
>
I guess it's some Nabble nonsense then...
>> A suitably
TE=en_US.utf8
> [5] LC_MONETARY=en_US.utf8LC_MESSAGES=en_US.utf8
> [7] LC_PAPER=CLC_NAME=C
> [9] LC_ADDRESS=C LC_TELEPHONE=C
> [11] LC_MEASUREMENT=en_US.utf8 LC_IDENTIFICATION=C
>
> attached base packages:
> [1] stats graphics grDevices utils datasets me
For some reason when I click on reply and sign-in - the message I'm replying
to is not carried forward. As you requested that include your message I
copied and pasted it from my email.
> A suitably comprehensive iconv function is essential. The R usage requires
> iconv to be able to translate
On 11-12-13 6:41 PM, Hervé Pagès wrote:
Hi Duncan,
On 11-12-10 05:27 AM, Duncan Murdoch wrote:
On 11-12-09 4:41 PM, Hervé Pagès wrote:
Hi Duncan,
On 11-12-09 11:39 AM, Duncan Murdoch wrote:
On 09/12/2011 1:40 PM, Hervé Pagès wrote:
Hi,
x<- c(rep(180003L, 1000), -rep(120002L, 15
13 matches
Mail list logo
