I'm not sure what your sticking point here is. If mpi does not modify
data in a (char *) pointer, then that really is a (const char *) pointer
and the headers are being unhelpful in not telling the compiler that
the data are constant.
If that is the case you need to use casts to (char *) and
On Fri, Sep 28, 2007 at 08:14:45AM -0500, Luke Tierney wrote:
[...]
[...] A related issue is that user-defined
assignment functions always see a NAMED of 2 and hence cannot modify
in place. We've been trying to come up with a reasonable solution to
this, so far without success but I'm
hi jeff,
i have read your paper from 2005 and your rapache solution sounds
good. i was wondering if u did sth about the state problem... you
should put a changelog on your website. what changes will come with
1.0?
and what is brew exactly for? it is like a tuned cat, mixing
r-output and text,
Hao Yu,
I spot two types of problematic code. Certainly the memcpy in
conversions.c:54 and 56 will cause problems, but I'm not sure whether
those functions are actually used?
The second paradigm is, e.g., Rmpi.c:561
MPI_Recv(CHAR(STRING_ELT(sexp_data,i)),
I noticed that R 2.7.0 will have as.Date.numeric with a second
non-optional origin argument. Frankly I would prefer that it default
to the Epoch since its a nuisance to specify but at the very least
I think that .Epoch should be provided as a builtin variable.
Greetings R'ers!
I have been looking for mathematics libraries for event stream processing /
time series simulation. Mathematics libraries for event stream processing
require two key features; 1) smart updates (functions use optimal update
algorithms, f.ex. once mean is calculated for an event
