public inbox for
help / color / mirror / Atom feed
Subject: guile/guile-core/guile-readline readline.c
Date: Tue, 11 Jan 2000 17:51:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/guile
Module name:	guile
Changes by:	00/01/11 17:51:14

Modified files:
	guile-core/guile-readline: readline.c 

Log message:
	* scm_validate.h: Added SCM_NUM2LONG_DEF macro.  Make
	SCM_OUT_OF_RANGE use SCM_MAKINUM, not scm_long2num.  Added
	macro.  Fix SCM_VALIDATE_STRINGORSUBSTR macro to not use SLOPPY
	* ports.c (scm_port_closed_p): Validate that the arg is a PORT,
	then return whether it's an open port (was validating that it was
	an open port -- this was a bug I introduced back in December, but
	my careful reading of diffs caught it).
	* numbers.c: Recombine the two conditional-compilation paths for
	all the log* primitives -- they were split based on #ifndef
	scm_long2num;  factored out a SCM_LOGOP_RETURN macro, and fixed
	some bugs and inconsistencies in the two sets of implementations.
	(scm_lognot) Fixed *atrocious* re-use of a SCM as an integer!
	* ioext.c: Use SCM_ASSERT_RANGE in a couple places, and
	SCM_VALIDATE_INUM_COPY once where it should've been used.
	* fluids.c (scm_internal_with_fluids): Use
	* filesys.c: Use SCM_NUM2LONG instead of SCM_VALIDATE_INUM_COPY;
	this is questionable as it relaxes type safety, but other changes
	were useful and all SCM_NUM2LONG's should probably be
	* evalext.c: line-break change on 1 line.
	* eval.c (nconc2last): Takes a non-empty list as its first
	argument, not just a list.
	* dynl.c: Use new SCM_COERCE_ROSTRING macro.

             reply	other threads:[~2000-01-11 17:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-11 17:51 gjb [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-18 17:48 mdj
2000-06-18 17:42 mdj
2000-06-14  8:03 mdj
2000-06-06  5:44 mdj
2000-05-01 15:12 ghouston
2000-03-12  8:02 mdj
2000-03-12  6:26 mdj
2000-03-11 16:35 mdj
2000-03-09 13:53 gjb
2000-03-09  8:00 gjb
2000-03-08 10:43 gjb
2000-01-09  9:01 mdj
2000-01-05 11:20 gjb
2000-01-05 11:06 gjb
1999-12-13 13:58 gjb
1999-12-12 19:57 gjb
1999-09-11  8:19 mvo
1999-08-29 14:07 mdj
1999-07-24  4:40 mdj

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:

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

  git send-email \ \ \ \

* 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).