Hi Spencer,
Sorry, I wasn't very clear in my initial post.
The function print.foo (myfoo, ...) won't pass R check (unless one
overwrites print first).
One has to write print.foo (x, ...), which in my personal opinion, can
be problematic.
In my oosp package, I have overwritten print (along with a
On Fri, Feb 12, 2010 at 8:01 PM, Guillaume Yziquel <
guillaume.yziq...@citycable.ch> wrote:
> Dominick Samperi a écrit :
>
>
>> Interesting, but what about the situation where a new author adds his name
>> as copyright holder without the
>> consent of the original copyright holder, and with only o
Dominick Samperi a écrit :
Interesting, but what about the situation where a new author adds his name
as copyright holder without the
consent of the original copyright holder, and with only one person making
the decision whether or not this
change is warranted: the new copyright holder? Doesn't
On Tue, Jan 19, 2010 at 11:54 AM, Simon Urbanek wrote:
> Copyright is the right that the author of an original work holds
> automatically (unless someone else can claim to own his work - e.g. his
> employer etc.) under the Berne Convention. The copyright gives only the
> author all rights - inclu
This post is to announce the 0.2 release of OCaml-R.
OCaml-R is a binding embedding the R interpreter into Objective Caml code.
Home page: http://home.gna.org/ocaml-r/
Download page: http://download.gna.org/ocaml-r/
Deb packages: http://yziquel.homelinux.org/debian/pool/main/o/ocaml-r/
Tutorial:
franz.quehenber...@medunigraz.at wrote:
Full_Name: Franz Quehenberger
Version: 2.10.1
OS: Windows XP
Submission from: (NULL) (145.244.10.3)
aggregate is supposed to produce a data.frame that contains a line for each
combination of levels of the variables in the by list. The first columns of th
Hi Simon and Peter
Ouch, I am sorry for raising this.
I hadn't even considered that this basic functionality might only have
entered R between 2.10 and 2.11 - and that trying to use it would not
raise an error pre-2.11.
The Windows PC was that of a student, which is a lame non-excuse for no
On 2/12/10 10:12 AM, Peter Ehlers wrote:
You're comparing 2.10.0 on Windows with 2.11.0 on Linux.
Have you tried 2.11.0 on Windows? => same result as on Linux.
Indeed, this is new functionality added to R-devel (5 Jan). Indexing an
n-dim array with an n-column matrix used to only be supported
On Feb 12, 2010, at 12:50 , Wolfgang Huber wrote:
Hi,
when running the following on different instances of R (Linux and
Windows), I get different results. The one for Linux seems to be the
intended / documented one. When using numeric indices rather than
characters, Windows seemed to beh
You're comparing 2.10.0 on Windows with 2.11.0 on Linux.
Have you tried 2.11.0 on Windows? => same result as on Linux.
-Peter Ehlers
Wolfgang Huber wrote:
Hi,
when running the following on different instances of R (Linux and
Windows), I get different results. The one for Linux seems to be th
On Feb 12, 2010, at 12:33 , blue sky wrote:
R-exts.pdf dosen't list many types that are supported in C++, for
example, long. Are there storage.mode corresponds to those extra
types?
There are none - that's why they are not listed. As for long: on 32-
bit platforms (and Win64) int and lo
Hi,
when running the following on different instances of R (Linux and
Windows), I get different results. The one for Linux seems to be the
intended / documented one. When using numeric indices rather than
characters, Windows seemed to behave as expected.
---On Windows--
R-exts.pdf dosen't list many types that are supported in C++, for
example, long. Are there storage.mode corresponds to those extra
types?
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Full_Name: Franz Quehenberger
Version: 2.10.1
OS: Windows XP
Submission from: (NULL) (145.244.10.3)
aggregate is supposed to produce a data.frame that contains a line for each
combination of levels of the variables in the by list. The first columns of the
result contain these combinations of lev
On 12/02/2010 10:33 AM, Barry Rowlingson wrote:
On Fri, Feb 12, 2010 at 2:22 PM, Simon Urbanek
wrote:
> This is getting OT, but, please, no XML. It's entirely useless in this
> context IMHO (as it is in others, but that's another story) and we already
> have reliable support for storing R objec
Hi, Charlotte:
I'm not sure what you mean. If you mean writing something like
"print.foo (myfoo, ...)", this is relatively benign I suppose, but I
avoid it where feasible. On multiple occasions, I've pushed
collaborators and even maintainers of other packages to change this or
allow
On Fri, Feb 12, 2010 at 2:22 PM, Simon Urbanek
wrote:
> This is getting OT, but, please, no XML. It's entirely useless in this
> context IMHO (as it is in others, but that's another story) and we already
> have reliable support for storing R objects (more than one in fact). Despite
> the fact tha
On 12 February 2010 at 09:22, Simon Urbanek wrote:
| On Feb 12, 2010, at 3:50 , Barry Rowlingson wrote:
|
| > On Wed, Feb 10, 2010 at 3:06 PM, Barry Rowlingson
| > wrote:
| >
| >> But I agree that writing a saveable options package is the first
| >> step
| >> - then making that a default in R
It is strange to me why the filename must start with a letter or
digit, while the following characters can be something like '['. Is
there a reason why it is designed in this way? So that I can
understand the design principle rather than memorizing the facts
derived from the principle.
On Fri, Feb
FYI,
a while ago I was looking into the "problem" with generic settings
files. I didn't find an omnibus/perfect solution, but have a look at
the Settings class in the R.utils package (R/Settings.R in the source
code). It tries to deal with automatic loading and saving of settings
(robust detecti
On Feb 12, 2010, at 3:50 , Barry Rowlingson wrote:
On Wed, Feb 10, 2010 at 3:06 PM, Barry Rowlingson
wrote:
But I agree that writing a saveable options package is the first
step
- then making that a default in R is the second so people don't have
to edit profiles and R packages and applic
On 12/02/2010 3:50 AM, Barry Rowlingson wrote:
On Wed, Feb 10, 2010 at 3:06 PM, Barry Rowlingson
wrote:
But I agree that writing a saveable options package is the first step
- then making that a default in R is the second so people don't have
to edit profiles and R packages and applications c
'Writing R Extensions' does say what names are allowed in the R
directory (at the start of section 1.1.3 in section-numbered formats).
To wit
The R subdirectory contains R code files, only. The code files to be
installed must start with an ASCII (lower or upper case) letter or
digit and h
On Wed, Feb 10, 2010 at 3:06 PM, Barry Rowlingson
wrote:
> But I agree that writing a saveable options package is the first step
> - then making that a default in R is the second so people don't have
> to edit profiles and R packages and applications can expect an API for
> savable state.
More
On Fri, Feb 12, 2010 at 5:35 AM, blue sky wrote:
> According to R-exts.pdf (page 3):
> For maximal portability filenames should only
> contain only ASCII characters not excluded already (that is
> A-Za-z0-9._!#$%&+,;=...@^(){}’[]
>
> I have some files with special characters like '[' and '%' e.g.
25 matches
Mail list logo
