I'd second Uwe's point. I was one of 31 signatories to first IEEE 754 (I didn't 
participate in
the two more recent releases, as I already tore my hair out with the details of 
low level
bit manipulations). Before the standard, porting code was truly a nightmare. We 
did it
because we had to and were too ignorant to realize what a fools task it was. 
Keep code
portable please.

JN

On 2021-12-06 6:07 a.m., Uwe Ligges wrote:


On 06.12.2021 03:09, Avraham Adler wrote:
Would this mean we could start using little endian bit strings, as I think
only the Solaris platform was big endian (or was it the other way around)?

It depends on the hardware, not the OS.
CRAN checked on Intel CPUs, which are little endian while formerly Solaris was 
typically used on Sparc which is big endian.

In any case, please try to write cross platform code further on. ARM and x86-64 may agree, but we do not know what comes next. And old ideas may be revived more quickly than expected: Not too many people expected 20 years ago that the future of scientific computing in 2021 would still/again happen on platforms without support for long doubles / extended precision.

Best,
Uwe Ligges



Avi

On Sun, Dec 5, 2021 at 8:56 PM Dirk Eddelbuettel <e...@debian.org> wrote:


On 5 December 2021 at 17:23, Travers Ching wrote:
| I see that there doesn't exist a Solaris flavor on any CRAN check page.
| However, I'm certain that Solaris was being checked up until very
recently.
|
| Is this just temporary?
|
| Is there any information for the future of Solaris on CRAN?

No "official" word yet on this list, r-devel or elsewhere, or via commits
to
the CRAN Policy (which a cron job of mine monitors).

But Henrik was eagle-eyed and spotted a number of changes to the svn (or
git
mirror thereof) writing Solaris out of the official documentation:

   https://twitter.com/henrikbengtsson/status/1466877096471379970

So yes it seems like an era is coming to a close.

Dirk

--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Reply via email to