# R for Windows will not send your bug report automatically.
# Please copy the bug report (after finishing it) to
# your favorite email program and send it to
#
# [EMAIL PROTECTED]
#
##
I am building a package. I discovered that all \usage
Hi,
I am considering if I should invest in learning R. Based on the
language definition and introductory documents, it seems nice. But now
I am faced with a problem: I want to be able to run R programs easily
from the unix shell, and write scripts that can automatically select R
as the interpreter
Full_Name: Göran Broström
Version: 2.3.1
OS: Linux, ubuntu
Submission from: (NULL) (85.11.40.53)
> dweibull(0, 0.5, 1)
[1] NaN
Warning message:
NaNs produced in: dweibull(x, shape, scale, log)
should give Inf (and no Warning). Compare with
> dgamma(0, 0.5, 1)
[1] Inf
This happens when 'shape'
Juha Vierinen wrote:
> Hi,
>
> I am considering if I should invest in learning R. Based on the
> language definition and introductory documents, it seems nice. But now
> I am faced with a problem: I want to be able to run R programs easily
> from the unix shell, and write scripts that can automati
Full_Name: Pat Lorch
Version: Version 2.3.1 (2006-06-01)
OS: OS X 10.4.7
Submission from: (NULL) (131.123.232.162)
I have noticed that when I save a Quartz graphic and sometimes when I source a
file, the dialog box persists and causes certain functions (Quit and Load/Save
Default Workspace) to b
Hi,
One of the big decisions when writing code is how to handle dates and
times. Gabor Grothendieck provided an excellent overview of the issue in
his R News 4/1 (2004) article, and many users and developers are probably
using it as a guide. The proposed guideline is to use the simplest class
re
On 14 July 2006 at 14:38, Sebastian Luque wrote:
| If Gabor's recommendations are to be followed, wouldn't it make sense to
| include chron in base R? Given that flexibility for handling time
Future historians will provide a fuller account of the extended debates, but
my reading of these discuss
On 7/14/06, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
>
> On 14 July 2006 at 14:38, Sebastian Luque wrote:
> | If Gabor's recommendations are to be followed, wouldn't it make sense to
> | include chron in base R? Given that flexibility for handling time
>
> Future historians will provide a full
Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
On 14 July 2006 at 14:38, Sebastian Luque wrote:
| If Gabor's recommendations are to be followed, wouldn't it make sense to
| include chron in base R? Given that flexibility for handling time
Future historians will provide a fuller account of the ext
On 14 July 2006 at 16:32, Gabor Grothendieck wrote:
| On 7/14/06, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
| > Date and POSIXt have served me well over the last few years. They are
| > maintained and being extended [ 1 ]. Chron, to the best of my knowledge, is
| > dead code so I'd bet against
[Sorry for my previous empty post]
Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
> On 14 July 2006 at 14:38, Sebastian Luque wrote:
> | If Gabor's recommendations are to be followed, wouldn't it make sense
> | to include chron in base R? Given that flexibility for handling time
> Future historia
On 7/14/2006 3:38 PM, Sebastian Luque wrote:
> Hi,
>
> One of the big decisions when writing code is how to handle dates and
> times. Gabor Grothendieck provided an excellent overview of the issue in
> his R News 4/1 (2004) article, and many users and developers are probably
> using it as a guide
12 matches
Mail list logo
