public inbox for guile-cvs@sourceware.org
help / color / mirror / Atom feed
From: gjb@sourceware.cygnus.com
To: guile-cvs@sourceware.cygnus.com
Subject: guile/guile-core/libguile alist.c list.c
Date: Thu, 06 Jan 2000 10:00:00 -0000	[thread overview]
Message-ID: <20000106180034.710.qmail@sourceware.cygnus.com> (raw)

CVSROOT:	/cvs/guile
Module name:	guile
Changes by:	gjb@sourceware.cygnus.com	00/01/06 10:00:33

Modified files:
	guile-core/libguile: alist.c list.c 

Log message:
	* alist.c: minimize scope of the tmp variables, and initialize
	them when declared. The strange SCM_NIMP tests are replaced by
	SCM_CONSP tests that more closely reflect the intended semantics.
	However, we don't get a performance penalty here, because the
	SCM_CONSP test was performed by the ALISTCELL test anyway.  * The
	extremely ugly use of ASRTGO macros was removed: The calls to
	ASRTGO were not encapsulated by "#ifndef SCM_RECKLESS", but got a
	label parameter that only exists when SCM_RECKLESS is not defined.
	This works, because ASRTGO itself is defined in a way that it only
	makes use of the label parameter if SCM_RECKLESS is not defined
	(shudder!).  Does guile make at all use of the possibility to
	define SCM_RECKLESS?  * Codesize is likely to be reduced, since
	instead of two calls to SCM_ASSERT performed by the ALISTCELL test
	we now only get one test.
	
	* list.c: Use SCM_NNULLP, not SCM_NIMP as appropriate.  Also use
	SCM_NULLP instead of SCM_IMP.  Drop use of "register" keyword on
	some variables in `list?'.  Fix `reverse' and `reverse!'
	primitives to handle improper lists better.


                 reply	other threads:[~2000-01-06 10:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000106180034.710.qmail@sourceware.cygnus.com \
    --to=gjb@sourceware.cygnus.com \
    --cc=guile-cvs@sourceware.cygnus.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).