This is a travesty of the highest order. :-)
Sector Lisp is smaller than Sector Forth and it claims to have
garbage collection.

https://justine.lol/sectorlisp2/

Brian Fox schrieb am Montag, 12. Juni 2023 um 21:35:31 UTC+2:
> This is a travesty of the highest order. :-)
> Sector Lisp is smaller than Sector Forth and it claims to have
> garbage collection.
>
> https://justine.lol/sectorlisp2/

Sector Lisp has no numbers, Sector Forth has no lists.
Who jumps farther?

On Monday, 12 June 2023 at 20:35:31 UTC+1, Brian Fox wrote:
> This is a travesty of the highest order. :-)
> Sector Lisp is smaller than Sector Forth and it claims to have
> garbage collection.
>
> https://justine.lol/sectorlisp2/

For a bit of context just in case anyone was interested.
Sector forth == https://github.com/cesarblum/sectorforth

The readme references this link :
https://groups.google.com/g/comp.lang.forth/c/NS2icrCj1jQ

I happen to have these links which might be useful...

(1) https://groups.google.com/g/comp.lang.forth/c/ESZD4h1prcw/m/jFXN7dvtCFMJ
(2) https://groups.google.com/g/comp.lang.forth/c/YCl455v1SSU/m/aiVwIux5elMJ
(3) https://groups.google.com/g/comp.lang.forth/c/uBj9D_jduOU/m/4LxAh_muadMJ

NN schrieb am Donnerstag, 15. Juni 2023 um 00:35:05 UTC+2:
> On Monday, 12 June 2023 at 20:35:31 UTC+1, Brian Fox wrote:
> > This is a travesty of the highest order. :-)
> > Sector Lisp is smaller than Sector Forth and it claims to have
> > garbage collection.
> >
> > https://justine.lol/sectorlisp2/
> I happen to have these links which might be useful...
>
> (1) https://groups.google.com/g/comp.lang.forth/c/ESZD4h1prcw/m/jFXN7dvtCFMJ
> (2) https://groups.google.com/g/comp.lang.forth/c/YCl455v1SSU/m/aiVwIux5elMJ
> (3) https://groups.google.com/g/comp.lang.forth/c/uBj9D_jduOU/m/4LxAh_muadMJ

Another nice overview by Rod Pemberton:
https://groups.google.com/g/comp.lang.forth/c/KHw28PKZXUk/m/JrXcjrYshxAJ

On 19/06/2023 4:03 am, minforth wrote:
> NN schrieb am Donnerstag, 15. Juni 2023 um 00:35:05 UTC+2:
>> On Monday, 12 June 2023 at 20:35:31 UTC+1, Brian Fox wrote:
>>> This is a travesty of the highest order. :-)
>>> Sector Lisp is smaller than Sector Forth and it claims to have
>>> garbage collection.
>>>
>>> https://justine.lol/sectorlisp2/
>> I happen to have these links which might be useful...
>>
>> (1) https://groups.google.com/g/comp.lang.forth/c/ESZD4h1prcw/m/jFXN7dvtCFMJ
>> (2) https://groups.google.com/g/comp.lang.forth/c/YCl455v1SSU/m/aiVwIux5elMJ
>> (3) https://groups.google.com/g/comp.lang.forth/c/uBj9D_jduOU/m/4LxAh_muadMJ
>
> Another nice overview by Rod Pemberton:
> https://groups.google.com/g/comp.lang.forth/c/KHw28PKZXUk/m/JrXcjrYshxAJ

IMO the measure of a forth is the number of applications written with it.
Applications determine what functions a forth requires which is in turn
determined by the environment. ISTM if forth has a problem it's counting
beans (words) rather than meeting needs. When DX-Forth got to point where
I was spending more time writing applications, they better informed me as
to what should go into the kernel and what can be left out. Consequently
I don't have an '8080 Forth' but rather a 'Forth for CP/M' and so on.

In article <u6r801$2bdd1$1@dont-email.me>, dxforth <dxforth@gmail.com> wrote:
>On 19/06/2023 4:03 am, minforth wrote:
>> NN schrieb am Donnerstag, 15. Juni 2023 um 00:35:05 UTC+2:
>>> On Monday, 12 June 2023 at 20:35:31 UTC+1, Brian Fox wrote:
>>>> This is a travesty of the highest order. :-)
>>>> Sector Lisp is smaller than Sector Forth and it claims to have
>>>> garbage collection.
>>>>
>>>> https://justine.lol/sectorlisp2/
>>> I happen to have these links which might be useful...
>>>
>>> (1) https://groups.google.com/g/comp.lang.forth/c/ESZD4h1prcw/m/jFXN7dvtCFMJ
>>> (2) https://groups.google.com/g/comp.lang.forth/c/YCl455v1SSU/m/aiVwIux5elMJ
>>> (3) https://groups.google.com/g/comp.lang.forth/c/uBj9D_jduOU/m/4LxAh_muadMJ
>>
>> Another nice overview by Rod Pemberton:
>> https://groups.google.com/g/comp.lang.forth/c/KHw28PKZXUk/m/JrXcjrYshxAJ
>
>IMO the measure of a forth is the number of applications written with it.
>Applications determine what functions a forth requires which is in turn
>determined by the environment. ISTM if forth has a problem it's counting
>beans (words) rather than meeting needs. When DX-Forth got to point where
>I was spending more time writing applications, they better informed me as
>to what should go into the kernel and what can be left out. Consequently
>I don't have an '8080 Forth' but rather a 'Forth for CP/M' and so on.
>

Indeed. I made a kernel that closely resembles figForth regarding
functionality, introduced standard in, standard out, redirection
and added the file wordset.
The I wrote a lot of programs, i.a. 400+ projecteuler solutions.
What I needed, I've added to the library and make it work across
the now 7 viable versions.

Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat spinning. - the Wise from Antrim -

none albert schrieb am Dienstag, 20. Juni 2023 um 10:49:07 UTC+2:
> In article <u6r801$2bdd1$1...@dont-email.me>, dxforth <dxf...@gmail.com> wrote:
> >On 19/06/2023 4:03 am, minforth wrote:
> >> NN schrieb am Donnerstag, 15. Juni 2023 um 00:35:05 UTC+2:
> >>> On Monday, 12 June 2023 at 20:35:31 UTC+1, Brian Fox wrote:
> >>>> This is a travesty of the highest order. :-)
> >>>> Sector Lisp is smaller than Sector Forth and it claims to have
> >>>> garbage collection.
> >>>>
> >>>> https://justine.lol/sectorlisp2/
> >>> I happen to have these links which might be useful...
> >>>
> >>> (1) https://groups.google.com/g/comp.lang.forth/c/ESZD4h1prcw/m/jFXN7dvtCFMJ
> >>> (2) https://groups.google.com/g/comp.lang.forth/c/YCl455v1SSU/m/aiVwIux5elMJ
> >>> (3) https://groups.google.com/g/comp.lang.forth/c/uBj9D_jduOU/m/4LxAh_muadMJ
> >>
> >> Another nice overview by Rod Pemberton:
> >> https://groups.google.com/g/comp.lang.forth/c/KHw28PKZXUk/m/JrXcjrYshxAJ
> >
> >IMO the measure of a forth is the number of applications written with it.
> >Applications determine what functions a forth requires which is in turn
> >determined by the environment. ISTM if forth has a problem it's counting
> >beans (words) rather than meeting needs. When DX-Forth got to point where
> >I was spending more time writing applications, they better informed me as
> >to what should go into the kernel and what can be left out. Consequently
> >I don't have an '8080 Forth' but rather a 'Forth for CP/M' and so on.
> >
> Indeed. I made a kernel that closely resembles figForth regarding
> functionality, introduced standard in, standard out, redirection
> and added the file wordset.
> The I wrote a lot of programs, i.a. 400+ projecteuler solutions.
> What I needed, I've added to the library and make it work across
> the now 7 viable versions.

The gauntlet was "Look, I got a tiny LISP and a tiny Forth !!".

The prominent reponses were "Mine is bigger and proven!"

Men... ;-)

On 20/06/2023 8:20 pm, minforth wrote:
> none albert schrieb am Dienstag, 20. Juni 2023 um 10:49:07 UTC+2:
>> In article <u6r801$2bdd1$1...@dont-email.me>, dxforth <dxf...@gmail.com> wrote:
>>> On 19/06/2023 4:03 am, minforth wrote:
>>>> NN schrieb am Donnerstag, 15. Juni 2023 um 00:35:05 UTC+2:
>>>>> On Monday, 12 June 2023 at 20:35:31 UTC+1, Brian Fox wrote:
>>>>>> This is a travesty of the highest order. :-)
>>>>>> Sector Lisp is smaller than Sector Forth and it claims to have
>>>>>> garbage collection.
>>>>>>
>>>>>> https://justine.lol/sectorlisp2/
>>>>> I happen to have these links which might be useful...
>>>>>
>>>>> (1) https://groups.google.com/g/comp.lang.forth/c/ESZD4h1prcw/m/jFXN7dvtCFMJ
>>>>> (2) https://groups.google.com/g/comp.lang.forth/c/YCl455v1SSU/m/aiVwIux5elMJ
>>>>> (3) https://groups.google.com/g/comp.lang.forth/c/uBj9D_jduOU/m/4LxAh_muadMJ
>>>>
>>>> Another nice overview by Rod Pemberton:
>>>> https://groups.google.com/g/comp.lang.forth/c/KHw28PKZXUk/m/JrXcjrYshxAJ
>>>
>>> IMO the measure of a forth is the number of applications written with it.
>>> Applications determine what functions a forth requires which is in turn
>>> determined by the environment. ISTM if forth has a problem it's counting
>>> beans (words) rather than meeting needs. When DX-Forth got to point where
>>> I was spending more time writing applications, they better informed me as
>>> to what should go into the kernel and what can be left out. Consequently
>>> I don't have an '8080 Forth' but rather a 'Forth for CP/M' and so on.
>>>
>> Indeed. I made a kernel that closely resembles figForth regarding
>> functionality, introduced standard in, standard out, redirection
>> and added the file wordset.
>> The I wrote a lot of programs, i.a. 400+ projecteuler solutions.
>> What I needed, I've added to the library and make it work across
>> the now 7 viable versions.
>
> The gauntlet was "Look, I got a tiny LISP and a tiny Forth !!".
>
> The prominent reponses were "Mine is bigger and proven!"
>
> Men... ;-)

It should be big enough to be able to move things but not so big as to give
fantasies wings :)