[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-apl] GNU APL port for OpenBSD
From: |
enztec |
Subject: |
Re: [Bug-apl] GNU APL port for OpenBSD |
Date: |
Tue, 29 Aug 2017 12:34:20 -0600 |
apl on openbsd openbsd on rpi
nice to see openbsd shaking off the cobwebs
On Tue, 29 Aug 2017 19:30:56 +0200
Juergen Sauermann <address@hidden> wrote:
> Hi,
>
> the rational numbers are still quite new, so I would like to wait a little
> longer before
> making a new release.
>
> Rational numbers cannot become the default because some computations with them
> take considerably more time than their floating point counterparts - mainly
> due to GCD
> normalization.
>
> Giuseppe, I have added a link to your blog on our APL community page.
>
> /// Jürgen
>
>
> On 08/29/2017 02:33 AM, Elias Mårtenson wrote:
> Perhaps it's time for a new release? Or should it be delayed until the
> rational number support is stable enough to be default?
>
> On 29 Aug 2017 02:22, "Giuseppe Cocomazzi" <address@hidden> wrote:
> Hi Jürgen,
> thanks for your reply.
> Ported software on OpenBSD is submitted for inclusion in the so-called
> "port tree", basically a set of custom Makefiles by means of which
> ports can be automatically downloaded, built, packaged and installed
> with a single "make" command. The port tree is part of the operating
> system, and importing rolling releases from SVN is not an option.
> Therefore, the official releases on the GNU mirrors are perfectly fine
> for the goal. Furthermore, I feel more comfortable in submitting
> stable and mature releases, as another goal of the OS is stability,
> security and cleanliness.
>
> As I am also the maintainer of the port/package, I will update the
> port's Makefile every time a major release is announced.
>
> As for the link to my blog/notebook, I have been actively maintaining
> my homepage for 8 years, my hosting service is quite stable and I have
> intention to keep the page away from oblivion. I think then it is
> reasonably safe to refer to it.
>
> Thank you very much.
>
>
>