unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: snarfer guard macro name decision: SCM_MAGIC_SNARFER
Date: Thu, 14 Mar 2002 00:58:45 -0600	[thread overview]
Message-ID: <87ofhrfxei.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E16lODa-0005vh-00@giblet> (Thien-Thi Nguyen's message of "Wed, 13 Mar 2002 21:56:02 -0800")

Thien-Thi Nguyen <ttn@giblet.glug.org> writes:

> everything is checked in now.  please feel free to read the new docs,
> try the new guile-snarf, and complain loudly so weirdnesses can be fixed
> (when the going gets weird, the weird turn pro)...

Great.  I'll suspect I'll be your first customer :> I'll try
gnome-guile in the morning.

I got 1.4 working for the code I was having trouble with after
removing (read-enable 'positions) in the offending case, but this just
exposes a later failure, one I've seen before during 1.4's make check

  scm_must_realloc called with arg bignum, was gh_symbol2newstr

If I can get gnome-guile to work with 1.5 now, I'll try it and see if
it tells me anything more.

Thanks again.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

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


  reply	other threads:[~2002-03-14  6:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13  7:51 snarfer guard macro name decision: SCM_MAGIC_SNARFER Thien-Thi Nguyen
2002-03-13  9:26 ` Thien-Thi Nguyen
2002-03-13 19:15   ` Marius Vollmer
2002-03-13 21:28     ` Thien-Thi Nguyen
2002-03-13 22:00       ` Rob Browning
2002-03-13 22:58         ` Thien-Thi Nguyen
2002-03-14  0:12           ` Thien-Thi Nguyen
2002-03-14  5:44             ` Rob Browning
2002-03-14 18:48             ` Marius Vollmer
2002-03-14 20:44               ` Thien-Thi Nguyen
2002-03-14 23:35                 ` Marius Vollmer
2002-03-15  4:26                   ` Thien-Thi Nguyen
2002-03-15 15:56                     ` Thien-Thi Nguyen
2002-03-15 21:19                       ` Marius Vollmer
2002-03-14  5:56           ` Thien-Thi Nguyen
2002-03-14  6:58             ` Rob Browning [this message]
2002-03-14  7:17               ` Rob Browning
2002-03-14  9:32                 ` Thien-Thi Nguyen
2002-03-14 23:40             ` Marius Vollmer
2002-03-14 19:09       ` Marius Vollmer
2002-03-14 22:43         ` Thien-Thi Nguyen
2002-03-14 23:31           ` Rob Browning
2002-03-15 21:12           ` Marius Vollmer
2002-03-15 21:33             ` Rob Browning
2002-03-15 21:58               ` Marius Vollmer
2002-03-17 17:07                 ` Rob Browning
2002-03-18  0:07                   ` Marius Vollmer
2002-03-18  2:52                     ` Rob Browning
2002-03-20 21:11                       ` Marius Vollmer
2002-03-21 16:23                         ` Rob Browning
2002-04-24 20:07                           ` Marius Vollmer
2002-04-24 20:42                             ` Rob Browning

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=87ofhrfxei.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    /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).