>>> From: Marko Rauhamaa
>>> Date: Tue, 23 Jun 2015 11:08:23 +0300
>>> Cc: guile-user@gnu.org
>>>
>>> Michael Tiedtke :
POSIX isn't that important or useful anymore but "full access to
POSIX system calls" it has never been.
>>> What I'd like is a way to communicate open file descriptors
Eli Zaretskii :
From: Marko Rauhamaa
>> I'd like to produce Guile code that works on Linux. As it stands, I
>> can't.
>
> Of course you can: write it in C and load it via FFI.
Well, for that, I don't even need Guile; all I need is gcc.
It's a bit of a lame reason to have to escape out of S
(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. Objective-C
has /tell/ Racket has /send/ but Guile/GOOPS is missing /call/.
This is a first "raw" definition where the parameter /message
Michael Tiedtke :
> Perhaps it's better to recreate a clean object model without 3,000
> lines of C code like GOOPS. But then GOOPS really creates the illusion
> of an object oriented environment with a MOP ...
I'd stay away from GOOPS -- it's a leap away from functional
programming, IMO.
Here's
On 25/06/2015 00:07, Marko Rauhamaa wrote:
Michael Tiedtke :
Perhaps it's better to recreate a clean object model without 3,000
lines of C code like GOOPS. But then GOOPS really creates the illusion
of an object oriented environment with a MOP ...
I'd stay away from GOOPS -- it's a leap away f
