unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Paul Smith <psmith@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Guile support in GNU make
Date: Tue, 17 Jan 2012 18:26:00 -0500	[thread overview]
Message-ID: <1326842761.4484.5.camel@psmith-ubeta> (raw)
In-Reply-To: <87y5t6x875.fsf@gnu.org>

On Tue, 2012-01-17 at 23:42 +0100, Ludovic Courts wrote:
> It works as intended ;-) but hits a segfault fixed with this patch:

Doh!  I added a feature to make that allows you to define functions
separately (previously all functions had to be predefined in the static
table in functions.c) and moved the guile function code out of
function.c into guile.c for better encapsulation...

And introduced a bug.  Sigh.

Thanks for the catch.

> > I suppose one option would be to have #f translate to the string "#f"
> > and change the definition in make of "false" to be "either the empty
> > string OR the string #f".  Since "#" is a comment character in make it's
> > highly unlikely (although not impossible) someone would have that as a
> > valid value.
> 
> It is possible to write valid GNU Make code that generates strings
> containing “#”?

Yes; make supports escaping comment characters:

        ~$ cat > /tmp/x1.mk
        FOO = \#
        all: ; @echo 'FOO = $(FOO)'
        
        ~$ make -f /tmp/x1.mk
        FOO = #

But my suspicion is that people would rarely use it due to annoyance
factors.

Thanks for testing this!




  reply	other threads:[~2012-01-17 23:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-14 19:55 Guile support in GNU make 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 [this message]
2012-01-19 20:42             ` Ludovic Courtès
2012-01-19 22:14             ` Ludovic Courtès
     [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
2012-01-23  6:01       ` 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

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=1326842761.4484.5.camel@psmith-ubeta \
    --to=psmith@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).