From: Roland Orre <roland.orre@neurologic.se>
Subject: Re: sudden snarf-problem
Date: Sun, 18 Jul 2004 16:53:04 +0200 [thread overview]
Message-ID: <1090162384.6164.4.camel@localhost> (raw)
In-Reply-To: <1090152630.21651.15.camel@localhost>
The problem seems not to be snarf as such, it seems to be me, who
has come to believe that I can declare SCM_PROC over more than one row.
It showed that the actual reason the compiler didn't complain was
that I had changed the compiler to gcc-3.* and this compiler didn't
complain about the missing semicolons in the .x file (usually
I'm running 2.95).
On Sun, 2004-07-18 at 14:10, Roland Orre wrote:
> Suddenly semicolons were missing for each declaration in the
> .x file where the SCM_PROC was declared over more than one line
> in the source.
>
> Any idea what can be the cause?
>
> I haven't updated my guile for quite some time, but the system,
> as I'm running debian/unstable.
>
> The snarf command looks OK:
> /usr/local/guile/guile-1.7/libguile/guile-snarf -o user.x user.c \
> -DHAVE_CONFIG_H -O2 -I/usr/local/guile/guile-1.7/include
>
/Roland Orre
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-07-18 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 12:10 sudden snarf-problem Roland Orre
2004-07-18 14:53 ` Roland Orre [this message]
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=1090162384.6164.4.camel@localhost \
--to=roland.orre@neurologic.se \
/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).