From b.rowlingson at lancaster.ac.uk  Wed Jan 13 09:37:03 2010
From: b.rowlingson at lancaster.ac.uk (Barry Rowlingson)
Date: Wed, 13 Jan 2010 08:37:03 +0000
Subject: [Rd] seq.int broken (seq as well) (PR#14169)
In-Reply-To: <1467566599@web.de>
References: <1467566599@web.de>
Message-ID: <d8ad40b51001130037o2a2e7a96w59b97a2d66fa21f0@mail.gmail.com>

2010/1/11 Jens Oehlschl?gel <oehl_list at gmx.de>:
> Petr,
> This can have severe consequences like accessing beyond the limits of an array. If C-code is involved, this can crash R. In the worst case algorithms can silently do wrong. Being an admirer of R since its early days, I was shocked to see this, and as a consequence, I suggest we do our homework and suspend -- for a year or two -- any claims that R can be used productive such as SAS.

 Invalid Argument Error

 What does SAS do in these cases? How do you know? How do you know if
your SAS code isn't silently doing wrong? How do you know what caused
your SAS session to crash? How do you know what algorithms SAS uses
deep down inside?

 R gives you the source code, you can find these things out. The great
irony here is that SAS have "THE POWER TO KNOW" as a registered
trademark.

 Perhaps The R Foundation should trademark "THE POWER TO LEARN"?

Barry



[Rd] seq.int broken (seq as well) (PR#14169)
Barry Rowlingson