Re: Advice on ST-Object data-structure setup

2024-04-20 Thread ken . dickey
On 2024-04-20 02:49, Mikael Djurfeldt wrote: Have you looked at Guile's OOP system GOOPS? Thanks, Mikael. I have implemented a number of object systems, including CLOS style systems such as GOOPS. The mismatch here is in the overhead of the multimethod dispatch. I would like something

Re: Advice on ST-Object data-structure setup

2024-04-20 Thread Mikael Djurfeldt
Then, of course, mapping language onto another complex system is perhaps seldom a good idea. Still, it is one way to create a new type of object. And, generic functions on such objects could still provide for a nice implementation of Smalltalk, even if you can't map the OOP systems onto eachother.

Re: Advice on ST-Object data-structure setup

2024-04-20 Thread Mikael Djurfeldt
Hi Ken, Have you looked at Guile's OOP system GOOPS? Chances are that you would get many required mechanisms for free. You get classes that can be instantiated. You could possibly implement messages as generic functions. The generic messages/generic functions already support keyword arguments,

Re: Advice on ST-Object data-structure setup

2024-04-17 Thread ken . dickey
On 2024-04-17 09:34, Maxime Devos wrote: > LICENSE says 'Copyright (c) 2016', but some files date from 2024. It's a bit > inconsistent ... Do you mean that changes >2016 are public domain, or not > covered by BSD license, or the inconsistency is an oversight? Ah. Thanks. I used Larceny

RE: Advice on ST-Object data-structure setup

2024-04-17 Thread Maxime Devos
>is to get the mechanics working.  For this I > need to have an St-Object which is basically a Vector but which > answers #false to vector? and #true to st-object? > > [Note https://github.com/KenDickey/Crosstalk/blob/master/st-kernel.scm ] > > I note that one might change the T7 type-tag from

RE: Advice on ST-Object data-structure setup

2024-04-17 Thread Maxime Devos
LICENSE says ‘Copyright (c) 2016’, but some files date from 2024. It’s a bit inconsistent … Do you mean that changes >2016 are public domain, or not covered by BSD license, or the inconsistency is an oversight?

Re: Advice on ST-Object data-structure setup

2024-04-17 Thread ken . dickey
Basile, Thank you much for the thoughtful reply. On 4/16/24 23:14, ken.dic...@whidbey.com wrote: .. I am looking at porting a toy Smalltalk-in-Scheme implementation to Guile. On 2024-04-17 00:10, Basile Starynkevitch wrote: .. I think it depends upon your goals; I assume your x86-64

Advice on ST-Object data-structure setup

2024-04-17 Thread Basile Starynkevitch
(sorry, resending as plain text to guile-user) On 4/16/24 23:14, ken.dic...@whidbey.com wrote: Greetings, I am looking at porting a toy Smalltalk-in-Scheme implementation to Guile. [Note https://github.com/KenDickey/Crosstalk ]. On github I (Basile Starynkevitch) am

Re: Advice on ST-Object data-structure setup

2024-04-17 Thread Basile Starynkevitch
On 4/16/24 23:14, ken.dic...@whidbey.com wrote: Greetings, I am looking at porting a toy Smalltalk-in-Scheme implementation to Guile. [Note https://github.com/KenDickey/Crosstalk ]. On github I (Basile Starynkevitch) am https://github.com/bstarynk and contributing to

Advice on ST-Object data-structure setup

2024-04-16 Thread ken . dickey
Greetings, I am looking at porting a toy Smalltalk-in-Scheme implementation to Guile. [Note https://github.com/KenDickey/Crosstalk ]. The idea is for simplicity first, then making into a module and potentially evolving Smalltalk into a supported, compiled ",language" in the Guile way.