From: Marko Rauhamaa <marko@pacujo.net>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: Carlos Pita <carlosjosepita@gmail.com>,
David Thompson <dthompson2@worcester.edu>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: A couple of questions about goops method parameters
Date: Fri, 05 Sep 2014 23:44:04 +0300 [thread overview]
Message-ID: <871trpkdbf.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <CAMFYt2Zvt+ZgHe6WUpEhx9r2K5h1LQ0XCHZ_0wCX-MtwRraJ-w@mail.gmail.com> (Panicz Maciej Godek's message of "Fri, 5 Sep 2014 22:10:26 +0200")
Panicz Maciej Godek <godek.maciek@gmail.com>:
> I think that it is a big problem of Scheme, that it does not have any
> noncontroversial and commonly accepted way for creating named tuples.
That's what alists are. They may not be the most beautiful way to
represent data as S expressions but they sure are noncontroversial and
commonly accepted.
However, objects, in my opinion, are the antithesis of tuples. Objects
are the focal points of methods. Whether the black box contains data and
in what form is none of the rest of the world's concern.
IMO, GOOPS has two main flaws:
* It brings an object's data slots to the fore while brushing methods
aside. The object constructor syntax is more or less directly tied to
the data slots.
* It introduces a very strong, almost Linnaean, type system to Scheme,
where it seems out of place. I see no principal reason for such
classification. I don't declare my numbers in Scheme; why should I
declare my object types?
Marko
next prev parent reply other threads:[~2014-09-05 20:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 2:05 A couple of questions about goops method parameters Carlos Pita
2014-09-03 15:49 ` Carlos Pita
2014-09-03 16:47 ` Marko Rauhamaa
2014-09-03 18:05 ` Carlos Pita
2014-09-03 16:20 ` Panicz Maciej Godek
2014-09-05 8:32 ` Nala Ginrut
2014-09-05 12:47 ` Carlos Pita
2014-09-05 19:03 ` Panicz Maciej Godek
2014-09-05 19:12 ` David Thompson
2014-09-05 19:35 ` Panicz Maciej Godek
2014-09-05 19:55 ` David Thompson
2014-09-05 20:10 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 20:50 ` David Thompson
2014-09-07 10:33 ` Neil Jerram
2014-09-07 15:27 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 20:10 ` Panicz Maciej Godek
2014-09-05 20:18 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 20:37 ` Panicz Maciej Godek
2014-09-05 20:51 ` Marko Rauhamaa
2014-09-05 21:53 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 22:26 ` Marko Rauhamaa
2014-09-05 20:44 ` Marko Rauhamaa [this message]
2014-09-05 21:08 ` Panicz Maciej Godek
2014-09-05 22:14 ` Marko Rauhamaa
2014-09-06 8:53 ` Panicz Maciej Godek
2014-09-06 10:44 ` Taylan Ulrich Bayirli/Kammer
2014-09-06 11:27 ` Marko Rauhamaa
2014-09-06 11:54 ` Taylan Ulrich Bayirli/Kammer
2014-09-06 23:46 ` Panicz Maciej Godek
2014-09-07 0:20 ` Marko Rauhamaa
2014-09-07 12:57 ` Taylan Ulrich Bayirli/Kammer
2014-09-07 13:58 ` Marko Rauhamaa
2014-09-07 16:46 ` Taylan Ulrich Bayirli/Kammer
2014-09-07 19:49 ` Marko Rauhamaa
2014-09-07 23:13 ` Taylan Ulrich Bayirli/Kammer
[not found] ` <CAPjoZoc7X7s+keog6avP62yvgJyQ3Ma_jomhw6xQq_rK9jnhVw@mail.gmail.com>
2014-09-06 16:57 ` Nala Ginrut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871trpkdbf.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--cc=carlosjosepita@gmail.com \
--cc=dthompson2@worcester.edu \
--cc=godek.maciek@gmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).