From: Aaron VanDevender <sig@netdot.net>
Cc: guile-user@gnu.org, guile-sources@gnu.org
Subject: Re: guile.m4
Date: Tue, 13 Jun 2006 22:02:12 -0500 [thread overview]
Message-ID: <1150254132.2726.152.camel@lazlo.netdot.net> (raw)
In-Reply-To: <873be8si8v.fsf@ossau.uklinux.net>
On Wed, 2006-06-14 at 01:17 +0100, Neil Jerram wrote:
> > +GUILE_CHECK([GUILE_CORRECT_VERSION_P],
> > + [(exit (let loop ((v1 (map string->number (string-split (version) (string-ref \".\" 0))))
> > + (v2 (map string->number (string-split \"$1\" (string-ref \".\" 0)))))
>
> Can we use #\. instead of (string-ref "." 0), or is the former a
> nightmare to quote correctly?
I tried to escape it, and I couldn't figure it out. And from
guile.m4:GUILE_CHECK:
# Avoid using the character "#" since that confuses autoconf.
It may not be possible. I don't know.
> > + (cond ((and (null? v1) (null? v2)) 0)
> > + ((null? v1) 0)
> > + ((null? v2) 1)
> > + ((> (car v1) (car v2)) 0)
> > + ((< (car v1) (car v2)) 1)
>
> Shouldn't the (null? v1) case have the same polarity as the (< v1 v2)
> case (because absence == 0) ?
Yes, you are correct. It should be:
(cond ((and (null? v1) (null? v2)) 0)
((null? v1) 1)
((null? v2) 0)
((> (car v1) (car v2)) 0)
((< (car v1) (car v2)) 1)
(else (loop (cdr v1) (cdr v2))))))
I had it all figured out with #f's and #t's instead of 1's and 0's, but
then I couldn't get it to escape in autoconf, so I guess I messed it up
when I switched to 0's and 1's.
Good eyes.
--
sig@netdot.net
Plead the First.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-06-14 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:40 guile.m4 Aaron VanDevender
2006-06-14 0:17 ` guile.m4 Neil Jerram
2006-06-14 3:02 ` Aaron VanDevender [this message]
2006-06-15 0:57 ` guile.m4 Kevin Ryde
2006-06-15 1:59 ` guile.m4 Aaron VanDevender
2006-06-15 5:52 ` guile.m4 Stephen Compall
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=1150254132.2726.152.camel@lazlo.netdot.net \
--to=sig@netdot.net \
--cc=guile-sources@gnu.org \
--cc=guile-user@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).