On 01/07/2015 7:20 AM, Ei-ji Nakama wrote:
> hi,
>
> Index: leap_second/src/library/base/R/zdatetime.R
> ===
> --- leap_second/src/library/base/R/zdatetime.R(revision 68608)
> +++ leap_second/src/library/base/R/zdatetime.R(wor
hi,
Index: leap_second/src/library/base/R/zdatetime.R
===
--- leap_second/src/library/base/R/zdatetime.R(revision 68608)
+++ leap_second/src/library/base/R/zdatetime.R(working copy)
@@ -24,7 +24,8 @@
"1979-12-31", "
On 30/06/2015 7:04 PM, Paul Gilbert wrote:
>
>
> On 06/30/2015 11:33 AM, Duncan Murdoch wrote:
>> On 30/06/2015 5:27 PM, Lorenz, David wrote:
>>> There is something I'm really missing here. The function show is a
>>> standardGeneric function, so the correct way to write it as method like
>>> this
Hi Charles,
Probably for the same reason it doesn't have short int, short unsigned
int, long int, long unsigned int, long long int, long long unsigned int,
long double etc... There are many built-in types in C and, in order
to keep things simple, I guess the line had to be drew somewhere.
Said ot
On 30/06/2015 17:42, Charles Determan wrote:
This is strictly a curiosity question. I am aware the R doesn't possess a
float data type. I also don't mean to request that such functionality be
implemented as I'm sure it would require a large amount of work with
potential back compatibility confl
Hi Greg, I was referring to the single precision type. Your points were
what I expected. I just wanted to ask the R community if there was any
other reason than 'there wasn't any reason to implement it'.
Thanks,
Charles
On Tue, Jun 30, 2015 at 12:29 PM, Greg Snow <538...@gmail.com> wrote:
> My
My understanding is that R does have a float type, it is just called
"double" instead of "float".
If you are referring to a single precision floating point type, then R
does have the "as.single" function, but that does not really change
the way the number is stored, just sets a flag so that the pr
On 06/30/2015 11:33 AM, Duncan Murdoch wrote:
On 30/06/2015 5:27 PM, Lorenz, David wrote:
There is something I'm really missing here. The function show is a
standardGeneric function, so the correct way to write it as method like
this:
That describes methods::show. The problem is that the de
This is strictly a curiosity question. I am aware the R doesn't possess a
float data type. I also don't mean to request that such functionality be
implemented as I'm sure it would require a large amount of work with
potential back compatibility conflicts. But I wanted to know why R has
never had
On 30/06/2015 5:27 PM, Lorenz, David wrote:
> There is something I'm really missing here. The function show is a
> standardGeneric function, so the correct way to write it as method like
> this:
That describes methods::show. The problem is that the default print
mechanism isn't calling methods::s
There is something I'm really missing here. The function show is a
standardGeneric function, so the correct way to write it as method like
this:
setMethod("show", "Person", function(object) {
for an object of class "Person" for example.
Dave
On Tue, Jun 30, 2015 at 10:11 AM, wrote:
> Same thi
Same thing happens with S3 if you redefine print(). I thought that
code was actually calculating the function to call rather than the
symbol to use, but apparently not. Shouldn't be too hard to fix.
luke
On Tue, 30 Jun 2015, Hadley Wickham wrote:
On Tue, Jun 30, 2015 at 2:20 PM, Duncan Murdoch
On Tue, Jun 30, 2015 at 2:20 PM, Duncan Murdoch
wrote:
> On 30/06/2015 1:57 PM, Hadley Wickham wrote:
>> A slightly simpler formulation of the problem is:
>>
>> show <- function(...) stop("My show!")
>> methods::setClass("Person", slots = list(name = "character"))
>> methods::new("Person", name =
On 30/06/2015 1:57 PM, Hadley Wickham wrote:
> A slightly simpler formulation of the problem is:
>
> show <- function(...) stop("My show!")
> methods::setClass("Person", slots = list(name = "character"))
> methods::new("Person", name = "Tom")
> #> Error in (function (...) : My show!
Just to be c
A slightly simpler formulation of the problem is:
show <- function(...) stop("My show!")
methods::setClass("Person", slots = list(name = "character"))
methods::new("Person", name = "Tom")
#> Error in (function (...) : My show!
Hadley
On Tue, Jun 30, 2015 at 9:02 AM, Dean Attali wrote:
> Hi r-d
Given how much documentation is available on R coding in general, it is
surprising how little is available specifically on writing model code.
Researchers who come up with a new method of regression, and who want to
write an S3 model for that method, must currently go all the way back to the
Vena
Hi r-devel
If you define a function named `show` or attach a package with an exported
`show` function, then printing/vieweing S4 objects breaks. This is probably
because the `print` function calls `show`, which is now masked.
Example:
show <- function() {}
> setClass("Person", slots = list(name
17 matches
Mail list logo
