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 ChangeLog Makefile.a ...
Date: Sat, 11 Dec 1999 18:36:00 -0000	[thread overview]
Message-ID: <19991212023617.24180.qmail@sourceware.cygnus.com> (raw)

CVSROOT:	/cvs/guile
Module name:	guile
Changes by:	gjb@sourceware.cygnus.com	99/12/11 18:36:17

Modified files:
	guile-core/libguile: ChangeLog Makefile.am alist.c arbiters.c 
	                     async.c backtrace.c boolean.c chars.c 
	                     continuations.c debug.c dynl-dl.c 
	                     dynl-dld.c dynl-shl.c dynl.c dynwind.c eq.c 
	                     error.c eval.c evalext.c feature.c 
	                     filesys.c fluids.c fports.c gc.c gdbint.c 
	                     gsubr.c guardians.c hash.c hashtab.c init.c 
	                     ioext.c keywords.c lang.c list.c load.c 
	                     macros.c mallocs.c net_db.c numbers.c 
	                     objects.c objprop.c pairs.c pairs.h ports.c 
	                     posix.c print.c procprop.c procs.c ramap.c 
	                     random.c read.c regex-posix.c root.c 
	                     scmsigs.c simpos.c smob.c snarf.h socket.c 
	                     sort.c srcprop.c stacks.c stime.c strings.c 
	                     strop.c strports.c struct.c symbols.c tag.c 
	                     tags.h threads.c throw.c unif.c variable.c 
	                     vectors.c version.c vports.c weaks.c 
Added files:
	guile-core/libguile: scm_validate.h 

Log message:
	* *.c: Pervasive software-engineering-motivated rewrite of
	function headers and argument checking.  Switched SCM_PROC,
	SCM_PROC1 macros to be GUILE_PROC, GUILE_PROC1 (may change names
	later, but was useful to keep old versions around while migrate)
	that has docstrings and argument lists embedded in the GUILE_PROC
	macro invocations that expand into a function header.  Use lots of
	new SCM_VALIDATE_* macros to simplify error checking and reduce
	tons of redundancy.  This is very similar to what I did for Scwm.
	
	Note that none of the extraction of the docstrings, nor software
	engineering checks of Scwm is yet added to Guile.  I'll work on
	that tomorrow, I expect.
	
	* Makefile.am: Added scm_validate.h to modinclude_HEADERS.
	
	* chars.c: Added docstrings for the primitives defined in here.
	
	* snarf.h:  Added GUILE_PROC, GUILE_PROC1.  Added
	SCM_REGISTER_PROC to be like old SCM_PROC, though old SCM_PROC
	still remains for now.  Changed naming convention for the s_foo
	string name of the primitive to be s_scm_foo for ease of use with
	the macro.
	
	* scm_validate.h: Lots of new SCM_VALIDATE macros to simplify
	argument checking through guile.  Maybe some of these should be
	folded into the header file for the types they check, but for now
	it was easiest to just stick them all in one place.


             reply	other threads:[~1999-12-11 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-11 18:36 gjb [this message]
2000-03-17  5:37 dirk
2000-04-21  7:16 mdj
2000-05-16  5:11 dirk

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=19991212023617.24180.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).