unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: tomas@tuxteam.de
Cc: guile-user@gnu.org
Subject: Performance implications of having many methods? Re: get all available symbols in scheme
Date: Wed, 15 Jun 2016 19:57:31 +0200	[thread overview]
Message-ID: <87oa72s5bo.fsf@web.de> (raw)
In-Reply-To: <20160614064244.GA31042@tuxteam.de>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Hi Tomas,

tomas@tuxteam.de writes:

>> source liu writes:
>> > I wonder if there is some way to dump all available symbols in current
>> > enviroment [...]
>> It’s pretty hidden. The easiest way [...]
> [a blazing tour through Guile introspection follows]
>
> Not the OP here, but... wow, thanks, Arne!

Thank you for writing — I’m glad you like it!

It’s not all my own work, though: I have to thank the people in here and
in IRC who helped me understand it. They are pretty awesome!

What I missed was to note the use of (class-off OBJECT) to find the
value I put into the methods.

What I cannot give is performance information about the methods: There
are some important implications of having many methods, but I just don’t
know them.

>> I just added this to guile-basics: http://www.draketo.de/proj/guile-basics/#sec-2-5
> thanks again

Enjoy Guile, and Happy Hacking!
- Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2016-06-15 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 18:38 get all available symbols in scheme source liu
2016-06-13 19:22 ` Panicz Maciej Godek
2016-06-13 21:46 ` Arne Babenhauserheide
2016-06-14  6:42   ` tomas
2016-06-15 17:57     ` Arne Babenhauserheide [this message]
2016-06-13 22:07 ` Taylan Ulrich Bayırlı/Kammer

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=87oa72s5bo.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-user@gnu.org \
    --cc=tomas@tuxteam.de \
    /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).