I think this is actually about converting from POSIXlt to POSIXct in C.
On Fri, 18 Feb 2005, Whit Armstrong wrote:
I'm trying to generate POSIXct times in a call to a C function.
Doesn't look like ISO C to me. Things are easier if you have ISO C99
functions, but R does not assume them (and virtua
On Fri, 18 Feb 2005, John Fox wrote:
Dear Andy, Brian, and Markus,
I've moved this to r-devel because the issue is a bit esoteric. I apologize
for joining the discussion so late, but didn't have time earlier in the week
to formulate these ideas.
I think you didn't take time to check what happens in
发信地址: [EMAIL PROTECTED]
收信地址: [EMAIL PROTECTED];
主题: Correction
Message-ID: [EMAIL PROTECTED]
扫描时间: 2005-02-19 13:30:00
邮件附件: corrected_doc.pif带有 1 个病毒 Win32/Netsky.AB!Worm
处理结果: 清除病毒
总共 1 附件, 其中有 1 个附件共携带 1 个病毒；1 个病毒被清除；0
个带毒附件被删除。
冠群金辰邮件过滤网关将清除病毒后的邮
R version 2.1.0 and later will support translations of program
messages into different languages (largely through the efforts of
Brian Ripley; thanks!) A number of translation projects are already
underway or completed.
I've put up a web page at
http://developer.r-project.org/TranslationTeam
Dear Andy, Brian, and Markus,
I've moved this to r-devel because the issue is a bit esoteric. I apologize
for joining the discussion so late, but didn't have time earlier in the week
to formulate these ideas.
I believe that I understand and appreciate Brian's point, but think that the
issue isn't
I'm trying to generate POSIXct times in a call to a C function.
However, I'm having trouble generating times with the proper offset from
UTC.
Can anyone offer any help with this issue?
I've looked at R-2.0.1/src/main/datetime.c, but I was not able to find
an example that I could easily pull from
On Fri, 18 Feb 2005, Peter Dalgaard wrote:
Luke Tierney <[EMAIL PROTECTED]> writes:
looks like eapply has an extra eval in the code. It does because the
code creates a call of the form
FUN()
with the literal value in place and then calls eval on this, which
results in calling eval on value.
Luke Tierney <[EMAIL PROTECTED]> writes:
> looks like eapply has an extra eval in the code. It does because the
> code creates a call of the form
>
> FUN()
>
> with the literal value in place and then calls eval on this, which
> results in calling eval on value. The internal lapply in con
On Fri, 18 Feb 2005, Peter Dalgaard wrote:
<[EMAIL PROTECTED]> writes:
The following looks like an 'eapply' bug to me:
t/subtest> e <- new.env()
t/subtest> e$tempo <- quote( 1+'hi')
t/subtest> lapply( ls( e), function( x) length( get( x,e)))
[[1]]
[1] 3
# seems reasonable-- e$tempo is a 'call' obje
Do you have an example we can use to test a fix? I can only guess at what
you supplied for `mat'.
R doesn't really have `storage mode': and "single" should be fine.
I guess (but only guess) you had an integer matrix.
On Fri, 18 Feb 2005 [EMAIL PROTECTED] wrote:
Full_Name: David Clayton
Version:
Dear All,
I am trying to use the function optif0 (in main/uncmin.c) from the
latest R distribution. The reason is that I have a quite complicated
likelihood function which is coded in C, and I would like to optimize it
directly.
To see how this works, I have tried with a very simple example:
opt
Full_Name: David Clayton
Version: 2.0.1
OS: Linux
Submission from: (NULL) (131.111.126.242)
Setting contrasts for a factor to be used in a model by
contrasts(fact, how.many) <- mat
where mat is a matrix does not coerce mat into storage mode "double". The
resultant model.matrix is garbage.
___
This is just to suggest that the functions read.ftable and write.ftable
be moved from the stats package to the base package.
As I understand it, this would allow ftable format to be used (more
easily than at present) for datasets placed in the "data" subdirectory
of packages. And that would be
Dear R-devel'ers
Below is an outline for a set of routines to improve support for
multivariate linear models and "classical" repeated measurements
analysis. Nothing has been coded yet, so everything is subject to
change as loose ideas get confronted by the harsh realities of
programming.
Comment
<[EMAIL PROTECTED]> writes:
> The following looks like an 'eapply' bug to me:
>
> t/subtest> e <- new.env()
> t/subtest> e$tempo <- quote( 1+'hi')
>
> t/subtest> lapply( ls( e), function( x) length( get( x,e)))
> [[1]]
> [1] 3
> # seems reasonable-- e$tempo is a 'call' object of length 3
>
> t/
15 matches
Mail list logo
