Jason,
as Chuck Berry (to whom, *thanks* for 'do {...} while(0)'!) suggested,
using grep, or even grep executed from find, such as
find . -type f -exec grep -H "dpois" \{\} \; | less
(executed from the root of an R source tree), is your friend.
cheers, Greg
Martin, et al.,
> I think we should allow 'year' to be "double" instead, and so it
> could also be +Inf or -Inf and we'd nicely cover
> the conversions from and to 'numeric' -- which is really used
> internally for dates and date-times in POSIXct.
storing years as a double makes me worry slight
Gabe,
> Also, I would expect the year 1e50 and the "year" Inf to be functionally
> equivalent in meaning (and largely meaningless) in context.
indeed.
thanks, Greg
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
hi. i'd like to instantiate sed(1), send it some input, and retrieve
its output, all via pipes (rather than an intermediate file).
my sense from pipe and looking at the sources (sys-unix.c) is that is
not possible. is that true? are there any thoughts of providing such a
facility?
cheers, Greg
Simon,
> FWIW if you're on unix, you can use named pipes (fifos) for that:
i've always wondered what named pipes actually were. thanks!
cheers, Greg
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Gabor, thanks. yes, managing the two-way communication is always a bit
error-prone, as it depends on the input/output characteristics of the
two ends -- they either match, or deadlock. it's too bad if polling is
always *required* -- i'd think sometimes a programmer would be happy
blocking, though
Dirk,
> Octave had this already in the 1990s, see documentation for 'popen2' here:
thanks. unix that had since the 1970s... :)
cheers, Greg
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
+1
Avi Gross via R-devel wrote:
> Arguably, R was not developed to satisfy some needs in the way intended.
>
> When I have had to work with datasets from some of the social sciences I have
> had to adapt to subtleties in how they did things with software like SPSS in
> which an NA was done us
Adrian,
> If it was only one column then your solution is neat. But with 5-600
> variables, each of which can contain multiple missing values, to
> double this number of variables just to describe NA values seems to me
> excessive. Not to mention we should be able to quickly convert /
> import /
luke,
> PLEASE DO NOT DO THIS!
very happy to withdraw my offered alternative!
cheers, Greg
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Taras,
> P.S. If you are wondering what I am trying to achieve here — we have a
> very large codebase and I am trying to use environments as a type of
> “poor man’s namespaces” to organize code in a modular fashion. But of
> course it’s all pointless if I can’t get the generics to work
> reliably.
Taras,
> That was my original plan as well, but managing and deploying dozens
> of little packages that are all under active development is a
> nightmare even with devtools. Just too much overhead, not to mention
> that coming up with names that would not have namespace conflicts was
> getting sill
Gabor Grothendieck wrote:
> ... and maybe not having a guarantee would simplify implementation?
+1 for: "The results of such statements are not defined.", or something
to that effect. (Erasmus had something to say here. :)
__
R-devel@r-project.org ma
personal development tree to a
tree from which the package can be passed to "R CMD *". do "you" have a
makefile in their tree that creates this? during development, is this
the path you use for building and testing?
cheers, Greg Minshall
thanks! that, as did an off-list reply, gave me the clue i needed.
cheers.
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
ed
(whereas if i remove DESCRIPTION.in and recreate the tar file,
everything is good.)
are there any thoughts on what might be the problem?
cheers, Greg Minshall
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file&q
hi, Duncan,
thanks for the reply, and the pointer to the XML package.
> I don't understand why configure needs access to DESCRIPTION.in. What
> is it reading there?
actually, ./configure is setting the version number in DESCRIPTION,
using DESCRIPTION.in as a template. in configure.ac, i have:
-
Duncan,
> That looks like a good fix in any case. I'll put it in. (It's too
> late to make it into 3.1.1, but I'll try to remember to backport it to
> R-patched after the release.)
great -- thanks!
cheers, Greg Minshall
s. a sample size
of 1 is *always* my favorite. :)
cheers, Greg Minshall
--- src/library/tools/R/QC.r2014-03-25 01:15:06.0 +0200
+++ src/library/tools/R/mod-QC.r2014-07-06 14:05:46.0 +0300
@@ -4372,6 +4372,9 @@
i'd like to consider these writable. assuming
sufficient warnings in the documentation, etc., is that permissable?
cheers, Greg Minshall
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
hi. i'm working on a package which only works if one (or both) of two
libraries (Imlib2 and MagickWand) exist on the machine on which the
package is compiled and executed. as currently written, the program
purposely generates an error at *compile* time if neither library is
available (thinking th
is package to CRAN? in
general, builds will fail, unless the build machine happens to have one
or both of the underlying libraries on it. (and, if i made it *compile*
successfully -- fairly easy to do -- then the tests will fail or, if the
tests *don't* fail, what were they testing?? :)
che
22 matches
Mail list logo
