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 Makefile.am alist.c  ...
Date: Sun, 12 Dec 1999 19:40:00 -0000	[thread overview]
Message-ID: <19991213034023.24704.qmail@sourceware.cygnus.com> (raw)

CVSROOT:	/cvs/guile
Module name:	guile
Changes by:	gjb@sourceware.cygnus.com	99/12/12 19:40:23

Modified files:
	guile-core/libguile: Makefile.am alist.c coop-threads.c debug.c 
	                     dynl.c dynwind.c error.c eval.c evalext.c 
	                     filesys.c fports.c gc.c guile-doc-snarf.awk 
	                     hash.c hashtab.c ioext.c keywords.c list.c 
	                     load.c macros.c net_db.c numbers.c 
	                     objprop.c ports.c posix.c procprop.c 
	                     procs.c ramap.c regex-posix.c root.c 
	                     scmsigs.c simpos.c socket.c stacks.c 
	                     stime.c strings.c strop.c strports.c 
	                     struct.c symbols.c threads.c throw.c unif.c 
	                     vectors.c version.c vports.c weaks.c 

Log message:
	* Makefile.am: Fix ETAGS_ARGS to recognize GUILE_PROC,
	GUILE_PROC1.  Build guile-procedures.txt, and add that file to
	pkgdata_DATA.
	
	* load.c: Added `pkgdata-dir', `site-dir', `library-dir'
	primitives.
	
	* guile-doc-snarf.awk: Drop trailing space when no arguments:
	e.g., "(foo )" is now "(foo)".
	
	* *.c: moved all the documentation for primitives from
	guile-doc/ref/{appendices,posix,scheme}.texi into the source code.
	This leaves about half of the primitives undocumented.  Also, all
	the markup is currently still texinfo.  I don't have a problem
	with texinfo per se, but the markup is not very descriptive or
	accurate.


                 reply	other threads:[~1999-12-12 19:40 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=19991213034023.24704.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).