similar to: Max value of an integer

Displaying 20 results from an estimated 5000 matches similar to: "Max value of an integer"

2015 Nov 18
3
Outdated information in regex.Rd
The NEWS for R-devel has the following item: > The previously included versions of zlib, bzip2, xz and PCRE have > been removed, so suitable external (usually system) versions are > required (see the ?R Installation and Administration? manual). Therefore I believe the following information in 'src/library/base/man/regex.Rd' is no longer valid: > If PCRE support was compiled
2016 May 18
3
[patch] Error in reg-tests-1c.R (R-devel)
I get an error when running "make check" after building R-devel r70629 on Ubuntu 14.04. Here are the relevant lines in the file "reg-tests-1c.Rout.fail": > ## m1z uses match(x, *) with length(x) == 1 and failed in R 3.3.0 > ## PR#16909 - a consequence of the match() bug; check here too: > dv <- data.frame(var?1 = 1:3, var?2 = 3); dv[,"var?2"]
2016 May 18
2
[patch] Error in reg-tests-1c.R (R-devel)
On 18/05/16 13:50, Martin Maechler wrote: >>>>>> Mikko Korpela <mikko.korpela at helsinki.fi> >>>>>> on Wed, 18 May 2016 13:05:24 +0300 writes: > > > I get an error when running "make check" after building > > R-devel r70629 on Ubuntu 14.04. > > Here are the relevant > > lines in the file
2017 Feb 23
2
Update copyright year in manuals
With new R releases soon to come, I suggest updating the Rcopyright macro in "doc/manual/R-defs.texi" to use year 2017. -- Mikko Korpela Department of Geosciences and Geography University of Helsinki
2018 Apr 26
1
Possible bug in package installation when R_ICU_LOCALE is set
(Belated) thanks for the confirmation, Ista. I just reported this issue on the R bug tracker: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17412 Best regards, - Mikko -----Alkuper?inen viesti----- L?hett?j?: Ista Zahn [mailto:istazahn at gmail.com] L?hetetty: 7. helmikuuta 2018 17:05 Vastaanottaja: Korpela Mikko (MML) Kopio: r-devel at r-project.org Aihe: Re: [Rd] Possible bug in
2016 Feb 29
3
Sys.readlink (on BSD vs Linux)
Hello, sorry for not being clear enough. My problem is represented with the following code, running on OSX: mkdir ~/test ln -s ~/test ~/testlink touch ~/test/foo Rscript -e 'Sys.readlink(c("~/test/foo", "~/testlink/foo")); normalizePath(c("~/test/foo","~/testlink/foo"))' I expected `Sys.readlink` to show the same output as `normalizePath`. Also,
2017 Feb 02
1
R Bugzilla down
The R Bugzilla at <https://bugs.r-project.org/bugzilla3/> is down, for at least some hours by now. The error message from my web browser reads: Can't connect to the database. Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Is your database installed and up and running? Do you have the correct username and password selected
2017 Feb 24
1
Update copyright year in manuals
On Thu, Feb 23, 2017 at 03:23:10PM +0100, Martin Maechler wrote: > >>>>> Mikko Korpela <mikko.korpela at helsinki.fi> > >>>>> on Thu, 23 Feb 2017 14:02:58 +0200 writes: > > > With new R releases soon to come, I suggest updating the > > Rcopyright macro in "doc/manual/R-defs.texi" to use year > > 2017. >
2016 Feb 29
2
Sys.readlink (on BSD vs Linux)
Hello together, the function `Sys.readlink` uses the system's readlink command to resolve symlink paths. On OSX/BSD the command has a different meaning than on Linux [1]. There exists the tool 'realpath', which seems suitable for the task, at least applied at the command line level [2]. It is used in `normalizePath`. I suggest (at least the latter) to * use realpath instead readlink
2016 Sep 27
2
library() asks user to accept license of some built-in packages
When 'getOption("checkPackageLicense")' is 'TRUE' and the user calls 'library(grid)' for the first time, R asks the user to either accept or decline the package license. This should not be necessary as the package license is "Part of R ..." with "..." denoting the R version number, and R is free and open source. The unnecessary license
2017 Feb 21
2
R CMD build error during vignettes build
Hello, I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31)) that has not seen any changes since it was last built without problems in previous R versions. It fails during vignette building with: ---<--------------------cut here---------------start------------------->--- $ R CMD build diveMove * checking for file ?diveMove/DESCRIPTION? ... OK * preparing ?diveMove?: *
2018 Sep 29
1
Improvement to documentation in dput.Rd
If the "Matrix" package is attached, 'example(dget)' fails: > library(Matrix) > example(dget) dget> fil <- tempfile() dget> ## Write an ASCII version of function mean to our temp file dget> dput(mean, fil) dget> ## And read it back into 'bar' dget> bar <- dget(fil) Error in initialize(value, ...) : '...' used in
2020 Aug 31
1
make check fails due to NA / NaN mismatch
It seems there is a problem in tests/d-p-q-r-tst-2.R (R-devel r79091): NA / NaN mismatch is not allowed by a test on lines 590--592, but the comment suggests otherwise. A run of "make check" fails there when tested on a Raspberry Pi with Raspberry Pi OS (based on Debian Buster): all 'NaN' is expected, but all 'NA' is returned when testing the function 'rf()' with
2016 Feb 25
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
On 23.02.2016 14:06, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code >>
2018 Dec 08
2
Possible encoding bug in sub()
I noticed that sub() gives unexpected results for the following test case. In the test case, the (initial) input is ASCII but the replacements are UTF-8. The first sub() produces an UTF-8 result with an "unknown" Encoding. This makes the result garbled in Windows (no UTF-8 locale there). The second sub() produces a correct result, although for some reason it is converted to the native
2018 Feb 07
1
Possible bug in package installation when R_ICU_LOCALE is set
On a Windows computer (other platforms not tested), installing a package from source may fail if the environment variable R_ICU_LOCALE is set, depending on the package and the locale. For example, after setting R_ICU_LOCALE to "fi_FI", install.packages("seriation", type = "source") (package version 1.2-3) fails with the following error: ** preparing package for
2016 Feb 29
1
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
I have just committed your first patch (the strlen() replacement) to R-devel, and will soon put it in R-patched as well. I wont have time to look at this again before the 3.2.4 release, so your file.show() patch isn't going to make it unless someone else gets to it. There's still a faint chance that I'll do more in R-devel before 3.3.0, but I think it's best if there were bug
2018 Mar 26
1
Typo in src/extra/tzone/registryTZ.c
I stumbled upon a typo in a time zone name: Irtutsk should be Irkutsk. A patch is attached. I also checked that this is the only bug of its kind in this file, i.e., all the other Olson time zones occurring in the file can also be found in Unicode Common Locale Data Repository. - Mikko Korpela Index: src/extra/tzone/registryTZ.c ===================================================================
2012 Jun 20
1
Possible bug in is.na.data.frame(): input without columns
Hello list! Let's construct a matrix / data.frame with 0 columns, but > 0 rows, and non-NULL rownames. Then, call is.na() on both the data.frame and the matrix. We find that is.na.data.frame() gives an error. When row.names are removed, is.na.data.frame() returns NULL. I think that the NULL result is also wrong. From ?is.na: The method ?is.na.data.frame? returns a logical matrix with
2016 Feb 24
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
On 23/02/2016 7:06 AM, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code