From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: API naming bugs
Date: Fri, 30 Dec 2005 19:54:08 +0000 [thread overview]
Message-ID: <87lky2cqe7.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <873bkawfkg.fsf@zagadka.de> (Marius Vollmer's message of "Fri, 30 Dec 2005 21:27:43 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> - scm_frame_begin, unwind_handler, etc -- should change because there
>> is also a SCM-based scm_frame interface
>
> Yeah, that's unfortunate. we have two things that are termed a
> "frame": he things dealt with by scm_frame_begin, etc, and the frames
> of a captured stack. When designing the scm_frame_begin stuff, I
> didn't think about those "other" frames, and when I finally noticed
> that there is a terminology overlap, ... I refused to think too much
> about it since I wanted to use the nice name for my stuff as
> well... Hmm. Ideally, I think the captured stack frames should be
> called "stack frames".
>
> Opinions?
Ideally, yes, but I think there is already a body of code using the
existing frame- names. (At least, I know I have such code in
guile-debugging, and I think others do too, because of the occasional
discussions about getting debugging information out of a stack.)
How about renaming the internal scm_frame functions instead, since
AFAIK they haven't been released yet? Perhaps scm_context_..., or
scm_dynwind_..., or scm_dc_...?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-12-30 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 0:44 API naming bugs Andy Wingo
2005-12-30 19:27 ` Marius Vollmer
2005-12-30 19:54 ` Neil Jerram [this message]
2006-01-28 22:54 ` Marius Vollmer
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=87lky2cqe7.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).