See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039051
In this bug report Peter Pentchev admits that he has neglected
gforth in Debian for decades.
albert@cherry.(none) (albert) writes:
See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039051
In this bug report Peter Pentchev admits that he has neglected
gforth in Debian for decades.
Or you can blame me, because I have not yet caught up
documentationwise with the state of Gforth 1.0 that we want to
document.
Or you can blame yourself:
https://gforth.org/
explains several ways to get a current snapshot (or to build from git,
but snapshots have the advantage of having passed more testing),
including getting and installing a .dep package or Docker image, so
you don't have to build it from the source.
What is the fault of the gforth package's maintainer prior to gcc-7
(about 2017): dynamic native code generation is disabled in the >Debian-distributed package, causing a slowdown. gcc-7 generates code
in a way that results in gforth-0.7 disabling dynamic native code
generation on its own. In the development version we have a
workaround for that.
- anton--
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html >comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: https://forth-standard.org/
EuroForth 2023: https://euro.theforth.net/2023
So, at least this first line should be corrected somehow. I assume that users often have a look for more up-to-date versions and go to the project's website. On Reddit, someone answered: But there this version is marked as latest release. That's theresult.
Sure, the best way would be a new adopter who really cares. But there are more ways to improve the situation than only waiting for a new adopter who might not come within the next years or so...
N. A. McBee (Kolloquia-DE) wrote:
So, at least this first line should be corrected somehow. I assume that users often have a look for more up-to-date versions and go to the project'swebsite. On Reddit, someone answered: But there this version is marked as latest release. That's the result.
Sure, the best way would be a new adopter who really cares. But there are more ways to improve the situation than only waiting for a new adopter who mightnot come within the next years or so...
You get what you pay for. And is it broken? Bits and bytes don't age.
It is similar to the TCC Tiny C Compiler. The "old" version
could even compile a Linux kernel. Still, many non-contributors
clamour for new releases with new features.
A bit unfair, don't you think?
It is similar to the TCC Tiny C Compiler. The "old" version
could even compile a Linux kernel. Still, many non-contributors
clamour for new releases with new features.
A bit unfair, don't you think?
The starting point of this discussion was that you get gforth v0.7.3 if you just type
apt install gforth
The reason is that the adopter of the gforth package did not adjust it to the latest version, that's all. (And didn't so for years...)
Nobody asked for more updates just for the sake of updates or something like that. The point is that the updates are there, Anton and his collaborators have
updated Gforth on their side this month (November 2023) and they have released many versions since 0.7.3. One only has to check the Gforth download page
accurately, then it is no problem at all to get the latest version.
I hope this clarifies my view ;) Thx!
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 46:49:32 |
Calls: | 6,710 |
Calls today: | 3 |
Files: | 12,243 |
Messages: | 5,354,363 |
Posted today: | 1 |