ple…” into a single warning, if appropriate (as in two of
the examples above), but that would require bigger surgery way above my
payscale.
I agree that in those cases it should only show one warning, and
to keep things simple I'd say it should just be the 2nd of those
above or more precisely
"regular" 1:n
integer row names which would be ALTREP compacted automatically
for non-small 'n'.
Last but not least, the check in tibble that was mentioned in
this thread, should almost surely be fixed, if gives a problem
for these example, and I claim it has been *that* code that has
buggy rather than base R's one.
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
handling also to C and have that happen *after* the C code looks
if it's an ALTREP object and if that "knows it's sorted".
Martin
> On Mon, Mar 15, 2021 at 12:01 PM SOEIRO Thomas
> wrote:
>> Hi Abby,
>>
>> Thank you for your
Getting back to this after 3 months :
>>>>> Martin Maechler
>>>>> on Wed, 16 Dec 2020 11:13:32 +0100 writes:
>>>>> Gabriel Becker
>>>>> on Mon, 14 Dec 2020 13:23:00 -0800 writes:
>> Hi Edgar, I certainly do
firefox (where I really typically only want one
firefox running, already being a crazy process generator and
sometimes memory hog).
The two (or more) different R processes are entirely autonomous
(in > 99.5% of cases), and I would rather have the current
proposal than a possibly quite a bit mo
e standard R x11 devices. I will try to attach a small screenshot,
we'll
> see how mailman likes it. Martin should still be able to get the old
(and to
> me, buggy) behaviour back by removing the one key line from the .desktop
> file, if his Fedora environment ever u
>>>>> Duncan Murdoch
>>>>> on Thu, 25 Mar 2021 10:41:46 -0400 writes:
> On 25/03/2021 9:18 a.m., Dirk Eddelbuettel wrote:
>>
>> On 24 March 2021 at 10:30, Martin Maechler wrote:
>> | For this reason I've committed t
> Brenton Wiernik
> on Tue, 13 Apr 2021 09:15:50 -0400 writes:
> In Microsoft’s Windows Subsystem for Linux (WSL or WSL2),
> there is not system framework, so utilities that depend on
> it fail. This includes timedatectl which R uses in
> Sys.timezone(). The timedatect
er that ... but none happened the last couple of weeks, so
R 4.1.0 and R-devel should be identical here.... but the CRAN
checks using R-devel don't seem to show anything.
...
... hence my deep puzzlement.
Thank you once more for the report,
Martin
--
Martin Maechler
ETH Zurich and R Core team
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
provides a (careful,
minimal, ..) patch, presumably to
src/library/tools/R/Rd2HTML.R
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
> Dénes Tóth
> on Wed, 21 Apr 2021 12:57:48 +0200 writes:
>
> Disclaimer: I sent this report first to r-package-de...@r-project.org
> but it seems it has not been delivered to the list - re-trying to r-devel
>
Also, for R-devel, your msg sat for 3 days i
e input had an Encoding(.) that was "fishy" in some sense
given the "context" (OS, locale, OS_version, ICU-presence, ...).
In particular, when the underlying code sees encoding-translation issues
for a string, NA would be returned instead of an error.
Martin
> On
oundation is the official 'R Foundation' twitter account
*and* that it also uses the Blog feed ..
> Looking forward to reading the new post.
Me too, thank you Lluís , for the "heads up"!
Martin
> Cheers,
> Lluís
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
7;s UseMethod().
Since R 4.0.0, we have provided R function .class2() to give
the same result as the internal R_data_class2(), and hence
show the classes (in the correct order!) which are really for S3
dispatch.
The NEWS entry for that was
\item New function \code{.class2()} provides
thod for the
corresponding class has been defined correctly; I've encountered
quite a few cases where people created vector-like classes but
did not provide a "correct" subsetting method (typically you
should make sure both a `[[` and `[` method works!).
Best regards,
Martin
Martin M
d
packages.
Note that for complete testing you will need a number of other
..
..
---
So, our (R core) own intent has been that 'make check' should
run w/o rec.packages but
> Jan Gorecki
> on Mon, 10 May 2021 12:42:09 +0200 writes:
> Hi R-devs,
> R 4.0.5 gives no warning. Is it expected? Searching the news for "I("
> doesn't give any info. Thanks
> z = I(getClass("MethodDefinition"))
Now what exactly did you intend with the above line ?
f R (of 25+ years).
Thank you!
I've already fixed this in the sources' trunk (svn rev 80321) a
minute ago; of course this will not make it anymore into R 4.1.0
but in its "patched" version, and then 4.1.1 and one.
With thankful regards,
Martin
--
Martin Maechler
ETH Zurich
ver on Linux based ones
(Ubuntu, Debian, Fedora, CentOS..), but maybe I'm too
optimistic there as well.
Note: I now also tried on our oldish Windows (Terminal) Server,
and it also just gave errors that it could not allocate so much
memory but did not produce a seg.fault.
Currently, I don'
>>>>> Ben Bolker
>>>>> on Wed, 9 Jun 2021 21:11:18 -0400 writes:
> Nice!
Indeed -- and thanks a lot, Dario (and Martin Morgan !) for
getting down to the root problem.
so, indeed a bug in Matrix (though "far away" from 'dgTMatrix').
g?
The "drawback" is of course that .Machine$integer.max is still
a function call (as R beginners may forget) contrary to L,
but that may even be inlined by the byte compiler (? how would we check ?)
and even if it's not, it does more clearly convey the concept
a
>>>>> Tomas Kalibera
>>>>> on Mon, 21 Jun 2021 10:08:37 +0200 writes:
> On 6/21/21 9:35 AM, Martin Maechler wrote:
>>>>>>> Michael Chirico
>>>>>>> on Sun, 20 Jun 2021 15:20:26 -0700 writes:
>> &
g in their requirement of getting rid of that
warning.
and as you've suggested in another thread, I should alleviate
the problem by uploading a new version of 'MatrixModels' models
to CRAN {solving another small unrelated buglet} so the warnings
will go away for everyone who updates their installed packages.
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
I have options(useFancyQuotes = FALSE) in my ~/.Rprofile.
Martin Morgan
On 7/13/21, 11:37 AM, "R-devel on behalf of Frederick Eaton"
wrote:
Dear R Team,
I am running R from the terminal command line (not RStudio). I've noticed
that R has been using Unicod
ds to be
changed.
Unless I get convincing suggestions for improvements, I'll commit
\item{expr}{a \dQuote{condition}. By default, and whenever not false
after being coerced to \code{\link{logical}}, the debugger will be
invoked, otherwise control is returned directly.}
(and also a
ged(res, "\\verb")
>
> There are probably other ways of fixing this problem, e.g. by only
> populating res if options$results != "hide" or only appending newlines
> if res is non-empty.
Thank you, Ivan, for the example and patch,
I
Dear Dominic,
This is the wrong mailing list for such questions
Do use 'R-help' or 'R-package-devel' instead, please.
(and also please do use __plain text__
instead of "formatted" / "rich text" / ... e-mail )
Best,
Martin Maechler
>>>>&
>>
> Looking at the history, this used to be cat() but got changed to a
message in R 3.2.0 (r65385, CCIng Martin in case he remembers the rationale for
warning vs message). I don't know for sure why it is not a warning, but I can
see that it is more in the line with infor
ce of deparse() in such cases:
NEWS has said
• New function deparse1() produces one string, wrapping deparse(),
to be used typically in deparse1(substitute(*)), e.g., to fix
PR#17671.
and the definition is a simple but useful oneliner
deparse1 <- function (expr, collapse = " &qu
I'm diverting this from R-help to R-devel,
because I'm asking / musing if and if where we should / could
change R here (see below).
>>>>> Martin Maechler on 11 Aug 2021 11:51:25 +0200
>>>>> Tim Taylor .. on 08:45:48 + writes:
>> Manipula
inverse cannot be computed
>
--
and similar for vcov(), of course, where the above error
originates.
{ I think GSoC (andr other) students should start by studying and
exploring relevant help pages before drawin
>>>>> J C Nash
>>>>> on Fri, 20 Aug 2021 11:41:26 -0400 writes:
> Thanks Martin. I'd missed the intention of that option,
> but re-reading it now it is obvious.
> FWIW, this problem is quite nasty, and so far I've found
>
that's "about ok" --
are there other things to consider?
Ideally, of course, the number of possible connections could be
increased dynamically only when needed
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
> GILLIBERT, Andre
> on Tue, 24 Aug 2021 09:49:52 + writes:
> RConnection is a pointer to a Rconn structure. The Rconn
> structure must be allocated independently (e.g. by
> malloc() in R_new_custom_connection). Therefore,
> increasing NCONNECTION to 1024 should only use
on("digits"), sep = " ", ...)
> {
> r <- stats:::format.ftable(x, quote = quote, digits = digits, ...)
> cat(t(r), file = file, append = append,
> sep = c(rep(sep, ncol(r) - 1), "\n"))
> invisible(x)
> }
I agree this
Hello,
All of the funprog functions except Position() use match.fun() early
in the body of the function. (Filter() seems to rely on lapply() for
this, but the effect is the same.) In most cases this isn't a problem,
but I can't see why Position() shouldn't look something like
Position2 <- functio
is able to ignore them). In any case they should
> probably be removed.
I've cleaned up now, indeed back compatibly, i.e., removing both
lines as you suggested.
Thank you, Hervé!
Martin
> Cheers,
> H.
> --
> Hervé Pagès
> Bioconductor Core Team
&g
lt; fuzz*nppm, na.rm = TRUE)) h[sml] <- 0
or rather we would define fuzz as
nppm * (k * .Machine$double.eps)
for a small k.
- - -
OTOH, type=7 is the default, and I guess used in 99.9% of
all uses of quantile, *and* does never use any fuzz
Martin
> --
> Sincerely
you say above.
{The experts typically use tryCatch() directly, instead of try() ,
which may be the reason other experienced R developers have not
stumbled over this ...}
Thanks a lot, notably also for the clear repr.ex. below.
Best regards,
Martin
> Example:
> fun <-
>>>>> Martin Maechler
>>>>> on Thu, 16 Sep 2021 17:48:41 +0200 writes:
>>>>> Alexander Kaever
>>>>> on Thu, 16 Sep 2021 14:00:03 + writes:
>> Hi,
>> It seems like a try(do.call(f, args)) can be very
to
yours, so we will almost surely change this (for R-devel;
possibly even consider "back" porting to R 4.1.1 patched).
Thank you for the report and suggestion,
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
ot;6" "7" "8" "9" "a" "b" "c" "d" "e" "f"
> as.character(as.hexmode(0:16))
[1] "00" "01" "02" "03" "04" "05" "06" "07"
trunc.Date() currently does
"behave as it should".
Martin Maechler
ETH Zurich and R Core
>>>>> SOEIRO Thomas
>>>>> on Thu, 30 Sep 2021 10:32:32 + writes:
> About fractional days, trunc.Date2 actually seems to have no regression
and to be ba
7)"
Note: During my experiments, I also do observe things confusing to me, when
using Rscript and R from the command line... in some cases
getting errors (in Japanese) ... but that may be just in those
cases I have left any space in the string
((in the case of 'R'
> Andrew Piskorski
> on Fri, 1 Oct 2021 05:01:39 -0400 writes:
> I recently built R 4.1.1 (Patched) from source, as I have many older
> versions over the years. This version, on Ubuntu 18.04.4 LTS:
> R 4.1.1 (Patched), 2021-09-21, svn.rev 80946, x86_64-pc-linux-gnu
) extended your (Travers') example into self
contained (no internet access) R script.
Bugzilla PR#18211 :" match() memory corruption "
https://bugs.r-project.org/show_bug.cgi?id=18211
with attachment 2929
--> https://bugs.r-project.org/attachment.cgi?id=2929&action=edit
ced at the
same when the type of 'len' in the R_SockWrite() header was
changed from int to size_t .. and the intent must have been to
do the same inside sock_write().
> Best,
> --
> Zafer
Thank you for the report!
Martin Maechler
ETH Zurich and R Core
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
e.g., from some do.call(). Thanks to Alexander Kaever's
suggestion posted to R-devel.
Martin
>>>>> nospam@altfeld-im de
>>>>> on Tue, 12 Oct 2021 12:11:10 +0200 writes:
> In fact an attentive user reported the same type of (slow due to depar
s(100, 7))
POISSON_7
2 3 4 5 6 7 8 9 10 11 12 13 14
4 5 14 16 20 8 8 13 1 5 3 2 1
R>
I'm fine if you move this to R bugzilla {where it remains more
easily findable in say 1 year's time}.
Thank you for the report and diagnosis so far!
Martin
t one \code{list} with its own \code{\link{names}()}, the internal
> function
With regards,
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
> GILLIBERT, Andre
> on Wed, 20 Oct 2021 08:10:00 + writes:
> Hello,
> That sounds like a good diagnosis!
> Indeed, R vectors are passed "by reference" to C code, but the semantic
must be "by value", i.e. the C function must NOT change the contents of the
vector, exc
>>>>> Martin Maechler
>>>>> on Wed, 20 Oct 2021 11:26:21 +0200 writes:
[]
> Thank you, André , that's very good.
> Just to state the obvious conclusion:
> If Ben's suggestion is correct (and André has explained
> Michał Bojanowski
> on Wed, 20 Oct 2021 16:31:08 +0200 writes:
> Hello Tomas,
> Yes, that's accurate although rather terse, which is perhaps the
> reason why I did not realize it applies to my case.
> How about adding something in the direction of:
> 1. Continu
> Duncan Murdoch
> on Thu, 28 Oct 2021 13:18:54 -0400 writes:
> This StackOverflow post: https://stackoverflow.com/q/69756236/2554330
> points out that objects created in one vignette are available in a later
> vignette. I don't think this should be happening: vignett
ot;.
Your proposal to have at least our deserialization code used in
readRDS() do (at least *some*) validity checks seems good, but
maybe we should think of more cases, and / or do such validity
checks already during serialization { <-> saveRDS() here } ?
.. Such questions then really are f
Jan 2005) | 2 lines
include \n in whitespace ignored for R-level gettext
I think this has been because simultaneously we had started to
emphasize to useRs they should *not* end message/format strings
in
>>>>> Martin Maechler
>>>>> on Fri, 5 Nov 2021 17:55:24 +0100 writes:
>>>>> Tomas Kalibera
>>>>> on Fri, 5 Nov 2021 16:15:19 +0100 writes:
>> On 11/5/21 4:12 PM, Duncan Murdoch wrote:
>>> On 05/11/2021 1
achieved (more
efficiently and naturally) by
gettext("Execution halted\n", domain="R", trim=FALSE)
but in any case, to *not* do the trimming anymore in general,
as I proposed yesterday (see below) is not a good idea.
>
>>> Martin Maechler
>>>>&
computations/approximations).
-> https://cran.r-project.org/package=DPQ
Best,
Martin
> sessionInfo:
> R Under development (unstable) (2021-11-15 r81196)
> Platform: x86_64-w64-mingw32/x64 (64-bit)
> Running under: Windows 10 x64 (build 19043)
rsight by me (back in March).
It's amazing nobody has seen the issue till now.
I've fixed it a bit more than 3 hours ago.
Thank you, Gábor !
Martin
--
Martin Maechler, ETH Zurich and R Core team
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
1-liner !}
Be assured that we agree that
quote(A + ~B + C~D)
should not "gain" any parentheses, indeed, and what you've been
seeing can well be considered an intermediate step in iterations
to get to improved deparsing in subtle situations.
Thank you for the report, and best regards,
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
matrix of the form cbind(i, j)
I agree that this could be improved in the Matrix package;
One reason this never happened is probably that we (the Matrix
package authors) never had a relevant use case for speeding
these up.
Would you be interested in collaboration to improve the Matrix
package
ther cases online where the extra precision and the
> different assembler code of FMA vs. non-FMA has caused
> bugs, such as [1]. Page 5 of this paper by Dr. William
> Kahan sheds some light on why this may be happening [2]
> (PDF).
> Martin & Morton, having
> Taras Zakharko
> on Tue, 7 Dec 2021 12:56:30 +0100 writes:
> I fully agree! General string interpolation opens a gaping security hole
and is accompanied by all kinds of problems and decisions. What I envision
instead is something like this:
> f”hello {name}”
> Which
>>>>> Martin Maechler
>>>>> on Tue, 7 Dec 2021 18:35:00 +0100 writes:
>>>>> Taras Zakharko
>>>>> on Tue, 7 Dec 2021 12:56:30 +0100 writes:
>> I fully agree! General string interpolation opens a gaping security hole
case ..
I'd have found that ugly to add. ... ...
... but of course, if you can prove that the code bloat would not be large
and not deteriorate speed in a measurable way and if you'd find
someone to produce a comprehensive and tested patch ...
Martin
> With best wishes,
> Ma
>>>>> Sokol Serguei on Thu, 9 Dec 2021 17:13:36 +0100 writes:
> On 09/12/2021 16:55, Ben Bolker wrote:
>>
>>
>> On 12/9/21 10:03 AM, Martin Maechler wrote:
>>>>>>>> Matthias Gondan
>>>>>>&g
ge developers to get their packaging problems
solved, notably to get advice in making their packages ready for
CRAN.
Julian's question was really addressing the whole R developer
community asking if some functionality was desirable to be added
to the R-package space.
For me one *the* approp
Linux, and even less relevant for any of the
other ways R is used interactively on non-Linux platforms. Maybe
it would also apply to *some* uses of R on the Mac, but not even
the default R-Mac GUI..
Sorry that this not as much encouraging as it probably should
be, but I though you'd rather want *
> Hi,
> currently I have to use
> compareVersion(as.character(packageVersion("shiny")), "0.11")
> It would be nice if compareVersion would make the as.character
> internally, rather then force the user to do it.
> Thanks
> Sigbert
Well, if you follow the help page examples of packageVersion(
'}' ) I've committed the help file
additions to the R sources (R-devel) in svn r81434 .
Thanks again and
"Happy New Year"
to all readers,
Martin
> On 12/26/21 8:35 PM, Balise, Raymond R wrote:
>> Hello R folks, Today I noticed that using the subs
ar}, without which no progress can be visible.
> \item \code{dimnames(table(d))} is more consistent in the case where
Thank you, Ben!
I will take care of this with my next commit (dealing with R's
bugzilla PR#18272).
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
indows?
... ah, searching the R sources reveals uses of %lld
*plus*
#ifdef Win32
#include /* for %lld */
#endif
so it seems we can and should probably change this ...
[Please, C compiler / library standard experts, chime in !]
Martin Maechler
ETH Zurich and R core team
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] compiler_4.2.0
(I have built my own R on macOS; similar behavior is observed on a Linux
machine)
Any hints welcome,
Martin Morgan
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
em-dashes, ...) would require special treatment. It seems like the right thing
to do is to handle the raw data in its original encoding, rather than to try to
clean it to ASCII.
Martin
On 1/5/22, 4:17 AM, "Tomas Kalibera" wrote:
Hi Martin,
I'd add few comments to t
>>>>> Tomas Kalibera
>>>>> on Mon, 3 Jan 2022 20:59:30 +0100 writes:
> On 1/3/22 6:15 PM, Martin Maechler wrote:
>>>>>>> Hugh Parsonage on Wed, 29 Dec 2021 00:36:51 +1100
>>>>>>> writes:
tation patch that adds the
> alternative version and a \seealso{} link.
>Happy to submit to r-bugzilla if requested.
>cheers Ben Bolker
x[DELETED ATTACHMENT external: reformulate_patch.txt, plain text]
Thanks a lot, Ben!
I've committed (+-) it to R-devel as svn rev 8146
I don't think this is a bug in the documentation. The help page for
`?[.data.frame` has the following in the last paragraph of the
details:
Both [ and [[ extraction methods partially match row names. By default
neither partially match column names, but [[ will if exact = FALSE
(and with a warning
a frame method ).
Faster in both cases, i.e., when there *is* a column and when there
is none (and NULL is returned), e.g., for the first case
> system.time(for(i in 1:2) df[["a"]])
user system elapsed
0.064 0.000 0.065
>
's
rbind.data.frame()
which now gives
> rbind(data.frame(a = 1, b = 2), c(3, 4, 5))
a b
1 1 2
2 3 4
Warning message:
In rbind(deparse.level, ...) :
number of columns of result, 2, is not a multiple of vector length 3 of arg 2
>
i.e., the same result, but *with* an informative warning,
analogously to the warning that has been produce "forever" in
the matrix case.
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
;)))
> Right now I'm using the following, which is ugly
> as.call(list(quote(`[`), quote(x), quote(index1), alist(x=)[[1]]))
Well, in such cases, much less ugly than both your version is to
use substitute(),
here e.g.,
> substitute(x[I,], list(I = quote(index1)))
x[inde
) function.
Also note that the documentation (the help page) is more or less
precise here, since as I said above, Scott did neither consider
dealing with the not so uncommon case of IQR() == 0.
But you are right that the help page could be more precise here
and make sure that the robustness app
ull accuracy.
Also, as you've noticed the R POSIX[cl]t code just truncates,
i.e. rounds towards 0 unconditionally, and I tend to agree that it
should rather round than truncate.
But we should carefully separate the issues here, from the
underlying inherent FAQ 7.31 truth t
est,
> Lluís
I agree and have added an entry there ... still to be
back ported to R 4.2.0 beta.
Martin
> On Tue, 12 Apr 2022 at 01:22, Gábor Csárdi wrote:
>>
>> I wonder if this change is intentional, and if it is, whether it is
>> worth mentioning
> Sebastian Fischer
> on Tue, 24 May 2022 09:01:17 +0200 writes:
> Dear R-devel Mailing List,
> I would like to get a better understanding of R's internal structures by
> using R's
> C API. For that I would like to have access to all the C header files
> that ar
exhibiting
bogous (and already fixed) behavior of the non-central t CDF:
https://rdrr.io/rforge/DPQ/src/tests/t-nonc-tst.R and
https://rdrr.io/rforge/DPQ/src/tests/pnt-prec.R
Indeed, this situation *can* be improved, but it needs dedicated work
of people somewhat knowledgable in applied ma
>>>>> Martin Maechler
>>>>> on Fri, 8 Jul 2022 16:34:43 +0200 writes:
>>>>> Michael Chirico via R-devel
>>>>> on Thu, 7 Jul 2022 22:17:12 -0700 writes:
>> SVN#80126 added rep.difftime, which means
>&g
nt hardwired behavior is documented.
4a) For as.POSIXlt.Date() to allow passing 'tz' needs changes
in the C code, i.e., is considerable more work than for the as.POSIXct(),
(or actually just post-processing in the R code, much less work)
4b) Only changing the behavior for as.POSIXc
>>>>> Kurt Hornik
>>>>> on Fri, 23 Sep 2022 09:57:49 +0200 writes:
>>>>> Martin Maechler writes:
> Currently in R-devel,
R> as.POSIXlt.Date
> function (x, ...)
> {
>if (any((y <- unclass(x)) > .Mach
*minimal*,
i.e., no white-space only changes etc
Thank you in advance for trying to make R better !
With regards,
Martin
--
Martin Maechler
ETH Zurich and R Core team
> --
> Sincerely
> Andr� GILLIBERT
> [[alternative HTML version deleted]]
___
>>>>> Martin Maechler
>>>>> on Fri, 23 Sep 2022 11:04:12 +0200 writes:
>>>>> Kurt Hornik
>>>>> on Fri, 23 Sep 2022 09:57:49 +0200 writes:
>>>>> Martin Maechler writes:
> > Currently in R-devel,
>
> Suharto Anggono Suharto Anggono via R-devel
> on Sun, 2 Oct 2022 08:42:50 + (UTC) writes:
> With r82904, 'as.character.POSIXt' in R devel is changed. The NEWS item:
> as.character() now behaves more in line with the
>methods for atomic vectors such as numbers, an
ented (or is it ??)
that the POSIXlt components should be thought to be recycling.
If we decide we want that,
once this is documented (and all methods/functions tested with
such POSIXlt) it could also be used to use considerably smaller size
POSIXlt objects, e.g, when all parts are in the same year, o
>>>>> Martin Maechler
>>>>> on Mon, 3 Oct 2022 14:46:08 +0200 writes:
>>>>> Suharto Anggono Suharto Anggono via R-devel
>>>>> on Sun, 2 Oct 2022 08:42:50 + (UTC) writes:
>> With r82904, 'as.character.P
in Date/Time objects.
> but this means the `NA` in the `mon` field is ignored.
which I agree is bogous and we'll fix.
Still, I did not get any feedback on asking about documentation
etc on POSIXlt objects ... and I *had* mentioned I agree
>>>>> Martin Maechler
>>>>> on Thu, 6 Oct 2022 10:15:29 +0200 writes:
>>>>> Davis Vaughan
>>>>> on Wed, 5 Oct 2022 17:04:11 -0400 writes:
>> Hi all,
>> I think I have discovered a bug in the con
>>>>> Davis Vaughan
>>>>> on Fri, 7 Oct 2022 11:00:23 -0400 writes:
> Martin,
> FWIW, I scoured the docs using GitHub's new code search preview but can't
> seem to find any reference to the fact that POSIXlt fields are internal
o be called via .Internal(.)
from a new R that provides this.
Provisionally called
balancePOXIXlt()
because it both balances the 9 to 11 list-components of POSIXlt
and it also puts all numbers of (sec, min, hour, mday, mon)
into a correct range (and also computes correctl wday
>>>>> Martin Maechler
>>>>> on Wed, 12 Oct 2022 10:17:28 +0200 writes:
>>>>> Kurt Hornik
>>>>> on Tue, 11 Oct 2022 16:44:13 +0200 writes:
>>>>> Davis Vaughan writes:
>>> I've got a bit mo
year = 116L, wday = 2L, yday = 340L, isdst = 1L))
> as.POSIXct(dlt)[1] is NA on Linux with timezone without DST. For example,
after
> Sys.setenv(TZ = "EST")
Hmm... I needed time to look at the above. Indeed, one gets NA
1001 - 1100 of 2286 matches
Mail list logo
