From: Paul Smith <psmith@gnu.org>
To: Kirill Smelkov <kirr@navytux.spb.ru>
Cc: Guile Users <guile-user@gnu.org>, make-alpha@gnu.org
Subject: Re: Guile support in GNU make
Date: Sun, 22 Jan 2012 16:56:19 -0500 [thread overview]
Message-ID: <1327269379.4539.41.camel@homebase> (raw)
In-Reply-To: <20120122182923.GB3460@mini.zxlink>
On Sun, 2012-01-22 at 22:29 +0400, Kirill Smelkov wrote:
> Then a bug report: running make check on taday's make from CVS and with
> guile-2.0 from Debian gives this:
>
> *** work/functions/guile.base Sun Jan 22 22:21:18 2012
> --- work/functions/guile.log Sun Jan 22 22:21:18 2012
> ***************
> *** 6,8 ****
> --- 6,13 ----
> bar
> a b
> a b c d 1 2 3
> +
> + Some deprecated features have been used. Set the environment
> + variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> + program to get more information. Set it to "no" to suppress
> + this message.
>
> I've tried to set that GUILE_WARN_DEPRECATED to "no", but the warning
> persists to stay. Perhaps it would be a good idea not to use deprecated
> features anyway...
Setting that variable doesn't do anything because the test suite strips
out all but a few "known good" variables.
So, maybe the Guile folks can give me some portability guidance. The
message Guile gives (when I set the above to "detailed") is this:
Guile used to use the wrong argument order for string-delete.
This call to string-filter had the arguments in the wrong order.
See SRFI-13 for more details. At some point we will remove this hack.
and it's because of this code in gmk-default.scm:
;; Printable string (no special characters)
((and (string? x)
(eq? (string-length (string-delete x char-set:printing)) 0))
x)
It's trying to determine if the string contains any non-printable chars.
How can I write this so it will work both with older Guile 1.8 and also
with newer Guile 2.0? Or, should I just forget about trying to work
with Guile <2.0? Most systems I have access to still have Guile 1.8
though.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@gnu.org> Find some GNU make tips at:
http://www.gnu.org http://make.mad-scientist.net
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
next parent reply other threads:[~2012-01-22 21:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1316557011.28907.237.camel@homebase>
[not found] ` <1326572016.3482.144.camel@homebase>
[not found] ` <20120122182923.GB3460@mini.zxlink>
2012-01-22 21:56 ` Paul Smith [this message]
2012-01-23 6:01 ` Guile support in GNU make Thien-Thi Nguyen
2012-01-23 6:08 ` Thien-Thi Nguyen
2012-01-29 20:05 ` Paul Smith
2012-01-31 19:17 ` Kirill Smelkov
2012-01-31 21:32 ` Paul Smith
2012-01-25 23:45 ` Ludovic Courtès
2012-01-14 19:55 Paul Smith
2012-01-15 8:51 ` Thien-Thi Nguyen
2012-01-15 12:33 ` Thien-Thi Nguyen
2012-01-15 16:12 ` Paul Smith
2012-01-15 20:11 ` Thien-Thi Nguyen
2012-01-15 20:49 ` Paul Smith
2012-01-15 22:02 ` Ludovic Courtès
2012-01-16 14:07 ` Paul Smith
2012-01-17 22:42 ` Ludovic Courtès
2012-01-17 23:26 ` Paul Smith
2012-01-19 20:42 ` Ludovic Courtès
2012-01-19 22:14 ` Ludovic Courtès
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=1327269379.4539.41.camel@homebase \
--to=psmith@gnu.org \
--cc=guile-user@gnu.org \
--cc=kirr@navytux.spb.ru \
--cc=make-alpha@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).