unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: API naming bugs
Date: Sun, 29 Jan 2006 00:54:28 +0200	[thread overview]
Message-ID: <873bj8x8t7.fsf@zagadka.de> (raw)
In-Reply-To: <87lky2cqe7.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 30 Dec 2005 19:54:08 +0000")

Neil Jerram <neil@ossau.uklinux.net> writes:

> How about renaming the internal scm_frame functions instead, since
> AFAIK they haven't been released yet?

Yep, I'll do that.

> Perhaps scm_context_..., or scm_dynwind_..., or scm_dc_...?

I'm going with scm_dynwind_ since the functions are directly related
to 'dynwind'.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2006-01-28 22: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
2006-01-28 22:54     ` Marius Vollmer [this message]

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=873bj8x8t7.fsf@zagadka.de \
    --to=mvo@zagadka.de \
    --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).