unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Sergey Poznyakoff <gray@Mirddin.farlep.net>
Cc: Rob Browning <rlb@defaultvalue.org>,
	rm@fabula.de, Han-Wen Nienhuys <hanwen@cs.uu.nl>,
	Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>,
	guile-devel@gnu.org
Subject: Re: Release Guile, now ;-) [was:] Re: GC rewrite, first version.
Date: Sun, 04 Aug 2002 23:57:24 +0300	[thread overview]
Message-ID: <200208042057.g74KvOb05512@Mirddin.farlep.net> (raw)
In-Reply-To: Your message of "Sun, 04 Aug 2002 13:43:49 PDT." <3D4D9205.8032FA18@pacbell.net>

> Which is exactly the problem.  Guile should *not* be exporting
> its config.h header.  Further, since Guile should not be doing
> it, anyone depending upon the Guile-configured values has mis-
> coded their program.  On that theory, the config header Guile
> exports should be free to prefix all its values.  Guile should
> do this.
[...]
> > Imagine a developer who wishes to use Guile as an extension
> > language for his package, he then would need to change almost all his
> > configuration suite.
> 
> To the contrary.  Guile needs to do this.

Agreed to both points. Another (yet related) question: Should
guile-doc-snarf stuff be installed to bin as guile-snarf is? I believe
it should. If a developer needs to use guile-snarf then he will surely
need to use guile-doc-snarf, yet the latter is a noinst_SCRIPTS
target. I guess this is inconsistent.

For example, the GNU radius project provides a set of scheme
primitives via SCM_DEFINE. To process the sources I need to include
in the package a copy of guile-doc-snarf (for version 1.4 as well as
for 1.6). It would be a lot easier if Guile had installed all the
snarfers.

Regards,
Sergey




_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-08-04 20:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-27 22:54 GC rewrite, first version Han-Wen
2002-07-28 16:40 ` Rob Browning
2002-07-29 20:11   ` Dirk Herrmann
2002-07-29 21:04     ` Rob Browning
2002-07-29 22:05       ` Han-Wen
2002-07-31 17:03         ` Dirk Herrmann
2002-07-31 18:02           ` Han-Wen Nienhuys
2002-07-31 21:15             ` Rob Browning
2002-08-01  9:20               ` Release Guile, now ;-) [was:] " rm
2002-08-01 16:27                 ` Rob Browning
2002-08-01 16:44                   ` rm
2002-08-01 18:37                   ` Sergey Poznyakoff
2002-08-01 22:21                     ` Rob Browning
2002-08-02  6:09                       ` Sergey Poznyakoff
2002-08-02 14:36                         ` Rob Browning
2002-08-02 17:29                           ` Sergey Poznyakoff
2002-08-02 18:10                             ` Bruce Korb
2002-08-02 19:50                               ` Rob Browning
2002-08-03  7:13                               ` Sergey Poznyakoff
2002-08-04 20:43                                 ` Bruce Korb
2002-08-04 20:57                                   ` Sergey Poznyakoff [this message]
2002-08-01 22:40                   ` Rob Browning
2002-08-02  9:35                     ` rm
2002-08-02 11:59                       ` rm
2002-08-02 15:00                         ` Rob Browning
2002-08-02 14:50                       ` Rob Browning
2002-08-01  9:59               ` Han-Wen Nienhuys
2002-08-01  8:46             ` Marius Vollmer
2002-07-31 18:46         ` Neil Jerram
2002-08-01  9:58           ` Han-Wen Nienhuys
2002-07-28 16:51 ` Michael Livshin

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=200208042057.g74KvOb05512@Mirddin.farlep.net \
    --to=gray@mirddin.farlep.net \
    --cc=dirk@sallust.ida.ing.tu-bs.de \
    --cc=guile-devel@gnu.org \
    --cc=hanwen@cs.uu.nl \
    --cc=rlb@defaultvalue.org \
    --cc=rm@fabula.de \
    /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).