unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: guile-user@gnu.org
Subject: A mess with GOOPS
Date: Fri, 2 Sep 2011 21:53:35 +0200	[thread overview]
Message-ID: <CAMFYt2bs5L+1xW4OJq8r5AOKUGjewvEiZtoitEMFjOB8s-=ERQ@mail.gmail.com> (raw)

Hi,
I've been using GOOPS with vectors now, and I've observed an annoying
feature. While "array-map!" et al. accept vectors, uvecs and arrays,
and so it is easy to write joint code for these types, this fact is
not reflected in the world of objects.
In other words, classes <vector>, <uvec> and <array> have nothing in
common, which requires me to triple the number of methods that could
accept any of these types.
If I would write any wrapping class hierarchy to embrace these
similarities, I would loose the advantage of having the special reader
extension for vectors and arrays, so I believe that this can be only
changed in the core of GOOPS.
Is there any possibility to do so?
Regards,
M.



             reply	other threads:[~2011-09-02 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 19:53 Panicz Maciej Godek [this message]
2011-09-03 13:01 ` A mess with GOOPS Andy Wingo
2011-09-05 21:35   ` Panicz Maciej Godek
2011-09-05 22:47     ` Panicz Maciej Godek
2011-09-06 10:17       ` Panicz Maciej Godek
2011-09-06 11:06         ` Panicz Maciej Godek
2012-01-09 17:11     ` Andy Wingo
2012-01-10 12:22       ` Daniel Llorens
2012-01-11 23:57         ` Daniel Llorens
     [not found] <mailman.173.1315324889.11781.guile-user@gnu.org>
2011-09-06 17:07 ` Daniel Llorens

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='CAMFYt2bs5L+1xW4OJq8r5AOKUGjewvEiZtoitEMFjOB8s-=ERQ@mail.gmail.com' \
    --to=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).