Hi Martin,
> On 22 May 2019, at 03:50, Martin Maechler wrote:
>
> I'm pretty sure that all teaching and documentation about S and R
> has suggested that print(f) and auto-printing should result in
> the same output _ AFAIR also for S4 objects
I agree with the principle that autoprint and pri
> Martin Maechler
> on Wed, 22 May 2019 09:50:10 +0200 writes:
> William Dunlap
> on Tue, 21 May 2019 12:11:45 -0700 writes:
>> Letting a user supply the autoprint function would be nice also. In a
way
>> you can already do that, using addTaskCallback(), but th
> William Dunlap
> on Tue, 21 May 2019 12:11:45 -0700 writes:
> Letting a user supply the autoprint function would be nice also. In a way
> you can already do that, using addTaskCallback(), but that doesn't let you
> suppress the standard autoprinting.
> Having the d
Letting a user supply the autoprint function would be nice also. In a way
you can already do that, using addTaskCallback(), but that doesn't let you
suppress the standard autoprinting.
Having the default autoprinting do its own style of method dispatch doesn't
seem right.
Bill Dunlap
TIBCO Softw
FWIW it was the intention of the patch to make printing of unclassed
functions consistent with other base types. This was documented in the
"patch 3" section:
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17398
I think we need a general way to customise auto-printing for base types
and even
It also is a problem with storage.modes "integer" and "complex":
3.6.0> print.integer <- function(x,...) "integer vector"
3.6.0> 1:10
[1] 1 2 3 4 5 6 7 8 9 10
3.6.0> print(1:10)
[1] "integer vector"
3.6.0>
3.6.0> print.complex <- function(x, ...) "complex vector"
3.6.0> 1
> William Dunlap via R-devel
> on Thu, 16 May 2019 11:56:45 -0700 writes:
> In R-3.6.0 autoprinting was changed so that print methods for the storage
> modes are not called when there is no explicit class attribute. E.g.,
> % R-3.6.0 --vanilla --quiet
>> print.funct
I don't know the answer to your question.
However, here's a side issue that may be relevant.
Last year, I tried creating my own ecdf object, and redefined the print
method for ecdf.
It worked ok in the console, interactively.
However, when I tried calling the method (with autoprinting) inside an
In R-3.6.0 autoprinting was changed so that print methods for the storage
modes are not called when there is no explicit class attribute. E.g.,
% R-3.6.0 --vanilla --quiet
> print.function <- function(x, ...) { cat("Function with argument list ");
cat(sep="\n", head(deparse(args(x)), -1)); i
