From: Andy Wingo <wingo@pobox.com>
Subject: API naming bugs
Date: Sun, 25 Dec 2005 19:44:10 -0500 [thread overview]
Message-ID: <1135557850.8094.8.camel@localhost.localdomain> (raw)
Hi,
A few potential API bugs.
1) functions that take C types normally are named scm_c_*. There are a
few exceptions though:
- scm_from_locale_symbol[n] -- here's a confusing name, perhaps
scm_c_symbol_from_locale_string is more apt -- but this function will be
used frequently, so there is an advantage to keeping it short; perhaps
scm_c_symbol_from_locale or scm_c_symbol_from_lstring or
scm_c_symbol_from_lchars?
- scm_frame_begin, unwind_handler, etc -- should change because there
is also a SCM-based scm_frame interface
2) NEWS talks about SCM_FRAME_WIND_EXPLICITELY, but code is (correctly)
EXPLICITLY
Regards,
--
Andy Wingo
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-12-26 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 0:44 Andy Wingo [this message]
2005-12-30 19:27 ` API naming bugs Marius Vollmer
2005-12-30 19:54 ` Neil Jerram
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=1135557850.8094.8.camel@localhost.localdomain \
--to=wingo@pobox.com \
/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).