From: Dirk Herrmann <dirk@ida.ing.tu-bs.de>
Cc: P Pareit <pieter.pareit@planetinternet.be>, bug-guile@gnu.org
Subject: Re: Name of scm_definedp not consistend with rest of names.
Date: Thu, 19 Sep 2002 21:35:34 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0209192132240.25951-100000@marvin.ida.ing.tu-bs.de> (raw)
In-Reply-To: <87ofaxlnei.fsf@zagadka.ping.de>
On 16 Sep 2002, Marius Vollmer wrote:
> P Pareit <pieter.pareit@planetinternet.be> writes:
>
> > Should scm_definedp() not better be called scm_defined_p() ?
>
> Well. The Lisp tradition is, iirr, that names that are one component
> get the "p" without an intervening dash, and names that are more than
> one component get the dash. That is, it would be "foop", but
> "small-foo-p". One could argue that scm_definedp has two components,
> or one could argue that the "scm_" prefix doesn't count...
>
> But as you say, consistency with the rest is more important. But
> backwards compatability is also important.
>
> I'd say it's OK to leave the names as it is.
I'd say introduce scm_defined_p for consistency, but keep the old version
as deprecated for some time. We don't have to get rid of it soon. This
could for example be scheduled for guile 2.0. Then, you have both
consistency and backwards compatibility.
Best regards
Dirk Herrmann
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-09-19 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 18:13 Name of scm_definedp not consistend with rest of names P Pareit
2002-09-16 19:55 ` Marius Vollmer
2002-09-19 19:35 ` Dirk Herrmann [this message]
2002-09-21 21:08 ` 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=Pine.LNX.4.21.0209192132240.25951-100000@marvin.ida.ing.tu-bs.de \
--to=dirk@ida.ing.tu-bs.de \
--cc=bug-guile@gnu.org \
--cc=pieter.pareit@planetinternet.be \
/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).