Re: Guile 1.8 / Viper System Interface

2015-06-26 Thread David Pirotte
Hello, Please let me know when you're interested in a cleaned up Guile 1.8 and the clean and lean Scheme path. None of us is interested in guile-1.8, please use guile-2, and if oop, please use goops. David pgpwte4tYjdwQ.pgp Description: OpenPGP digital signature

Re: Message Passing with GOOPS

2015-06-26 Thread Ralf Mattes
On Wed, Jun 24, 2015 at 10:21:44PM +0200, Michael Tiedtke wrote: (use-modules (oop goops)) GOOPS has some nice features (you can even use unexported methods with generics in 1.8) but there is no message passing paradigm. Guile's GOOPS is a (rather impressive) clone of CLOS, the Common Lisp

Re: Message Passing with GOOPS

2015-06-26 Thread Marko Rauhamaa
Pascal J. Bourguignon p...@informatimago.com: Marko Rauhamaa ma...@pacujo.net writes: Similarly, in my mind, objects don't have slots, they interact. You are right. Slots are an implementation detail. Notice that you have them in all (common) OO systems. But the difference with CLOS, with

Re: my current project: new lalr module

2015-06-26 Thread Matt Wette
On Jun 3, 2015, at 8:40 PM, Matt Wette matthew.we...@verizon.net wrote: My current project is a lalr module. Here is a slight update on my parser generator. 1) I have added a hashify procedure that allows one to set up the parser and lex'er to use integers instead of symbols. 2) I have

Re: Guile 1.8 / Viper System Interface

2015-06-26 Thread Michael Tiedtke
On 26/06/2015 21:36, David Pirotte wrote: Hi Michael, Sorry, you got me wrong. This is an announcement thread for those interested. None of us is interested in guile-1.8, please use guile-2 Cheers, David Sorry, today I exterminated elisp and emacs support from my 1.8 branch. Libtool is my

Re: Message Passing with GOOPS

2015-06-26 Thread Michael Tiedtke
On 26/06/2015 10:18, Ralf Mattes wrote: ... This is a first raw definition where the parameter /message/ has to be a quoted symbol. (define-method (call (receiver object) message . arguments) (apply (slot-ref receiver message) arguments)) The class definition still looks like

Re: Guile 1.8 / Viper System Interface

2015-06-26 Thread Michael Tiedtke
On 26/06/2015 08:39, David Pirotte wrote: Hello, Please let me know when you're interested in a cleaned up Guile 1.8 and the clean and lean Scheme path. None of us is interested in guile-1.8, please use guile-2, and if oop, please use goops. David Sorry, you got me wrong. This is an

Re: Message Passing with GOOPS

2015-06-26 Thread Marko Rauhamaa
Ralf Mattes r...@seid-online.de: Guile's GOOPS is a (rather impressive) clone of CLOS, the Common Lisp Object System. I such a system functions/methods don't belong to a class. [...] Message passing only exists in object systems where methods belong to a class/object. Generic functions

Re: Message Passing with GOOPS

2015-06-26 Thread Pascal J. Bourguignon
Marko Rauhamaa ma...@pacujo.net writes: GOOPS also, surprisingly, seems to be decades behind in trying to present objects as collections of slots. I once heard this story. The French king had a royal ball in honor of the birthday of the French queen. When some lordly guests presented their