unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Atom X <atomx@deadlyhead.com>
To: guile-user@gnu.org
Subject: Re: GOOPS question
Date: Fri, 30 Apr 2021 01:52:56 -0400	[thread overview]
Message-ID: <4F71F499-D823-4688-89A6-AFF8D3BF92F6@deadlyhead.com> (raw)
In-Reply-To: <CADEOadc09aequx31A7yQc8cYFta-WTH_Bp-qjWv3posOv5jcWw@mail.gmail.com>

Hi Damien,

On April 29, 2021 7:10:12 PM EDT, Damien Mattei <damien.mattei@gmail.com> wrote:
>hi,
>i want to create a growable vector class in Guile,
>such as std::vector or python list,
>first i do not know if it exist already? seems not
>

Regarding your immediate need for a growable vector type, Guile implements VLists <https://www.gnu.org/software/guile/manual/html_node/VLists.html>, which can take the place of standard lists, but also offer constant- time index referencing like vectors. VLists are functional data structures and are thus immutable, but this is natural for idiomatic Scheme code.

>i want to use GOOPS but i do not understand how the superclass could be
>accessed,used, instanciate...
>for example in the doc there is:
>(define-class <my-complex> (<number>) r i #:name "Complex")
>
>seems <number> superclass is of no use
>
>for my growable vector i would like to use array as superclass?
>but perhaps should it be just a slot as array are a subset of growable
>array ,so a subclass
>
>anyway if i write something ike that:
>(define-class <gvector> (<array>) .....
>how can i use the <array> object?
>
>i think perhaps i should not define a superclass or <object> as super
>class....
>any advice welcome...
>
>Damien

-- Atom



  reply	other threads:[~2021-04-30  5:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 23:10 GOOPS question Damien Mattei
2021-04-30  5:52 ` Atom X [this message]
2021-04-30  7:55 ` Mikael Djurfeldt
2021-05-02  0:07   ` Damien Mattei
2021-05-02 10:14     ` Damien Mattei
2021-05-02 10:26       ` Mikael Djurfeldt
2021-05-02 10:58         ` Damien Mattei
2021-05-02 10:34       ` Damien Mattei
2021-05-02 10:35       ` tomas
2021-05-02 10:21     ` Mikael Djurfeldt
2021-05-08 21:11       ` Damien Mattei
2021-05-10 12:22         ` Mikael Djurfeldt
2021-04-30  7:57 ` Linus Björnstam
2021-04-30  9:47   ` Damien Mattei
2021-04-30 10:43     ` Mikael Djurfeldt
2021-04-30 11:08 ` Mikael Djurfeldt
2021-04-30 12:19   ` Stefan Israelsson Tampe
2021-04-30 14:50     ` Mikael Djurfeldt
2021-04-30 15:15       ` Mikael Djurfeldt
     [not found] <Pine.GSO.4.05.10207071043010.9685-100000@sallust.ida.ing.tu-bs.de>
2002-07-08 18:26 ` goops question Marius Vollmer
     [not found] ` <87fzyu9iu0.fsf@zagadka.ping.de>
2002-07-08 19:59   ` Dirk Herrmann
2002-07-09 21:17   ` Neil Jerram
  -- strict thread matches above, loose matches on Subject: below --
2002-07-07  8:45 Dirk Herrmann

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=4F71F499-D823-4688-89A6-AFF8D3BF92F6@deadlyhead.com \
    --to=atomx@deadlyhead.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).