public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: guileapi.x problems [patch]
Date: Thu, 16 Mar 2000 16:57:00 -0000	[thread overview]
Message-ID: <874sa6v2if.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <m31z5a26tt.fsf@kei.cwru.edu>

Keisuke Nishida <kxn30@po.cwru.edu> writes:

> What would be the best?

I think it would be cleanest to put #ifndef SCM_MAGIC_SNARFER
around the #include: we don't want the behavior of guile-snarf to
depend on the previous contents of *.x.  After this, the Makefile
could be changed to use a temporary file.

Although the current version of guile-snarf defines
SCM_MAGIC_SNARFER, that macro doesn't seem to be documented
anywhere so relying on it is a bit risky.  If the Guile team
promises they won't remove this macro, all is well.  Such a
promise should be written down in the manual so that their
grandchildren won't forget it.  ;-)

  reply	other threads:[~2000-03-16 16:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-13 15:11 guile-emacs-0.1 released Keisuke Nishida
2000-03-14 12:46 ` guileapi.x problems [patch] Kalle Olavi Niemitalo
2000-03-14 13:20   ` Keisuke Nishida
2000-03-15 21:11   ` Ken Raeburn
2000-03-16  4:29     ` Kalle Olavi Niemitalo
2000-03-16  8:55       ` Keisuke Nishida
2000-03-16 16:57         ` Kalle Olavi Niemitalo [this message]
2000-03-17  9:55           ` Keisuke Nishida
2000-03-15 21:07 ` guile-emacs-0.1 released Ken Raeburn
2000-03-16 12:29   ` Keisuke Nishida
2000-03-16 18:50   ` Richard Stallman
2000-03-17  2:10     ` Ken Raeburn
2001-01-07  9:13       ` Richard Stallman
2001-01-07 13:28         ` Ken Raeburn

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=874sa6v2if.fsf@PC486.Niemitalo.LAN \
    --to=tosi@stekt.oulu.fi \
    --cc=guile-emacs@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).