[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #43378] $(guile ...) must be coaxed to accept (or does not accept)

From: Taahir Ahmed
Subject: [bug #43378] $(guile ...) must be coaxed to accept (or does not accept) valid guile code.
Date: Wed, 08 Oct 2014 00:27:14 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0


                 Summary: $(guile ...) must be coaxed to accept (or does not
accept) valid guile code.
                 Project: make
            Submitted by: ahmedtd
            Submitted on: Wed 08 Oct 2014 12:27:13 AM GMT
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: None
        Operating System: Any
           Fixed Release: None
           Triage Status: None



The $(guile) function does not accept all valid guile code.

For example, the sharps here are unconditionally interpreted as comments:

----make code snip----
libelektros_CFLAGS := $(guile (augmk/pkg-config/cflags "eigen3" #:sedsystem
----make code snap----

Sharps are fairly important syntactic components of guile --- they are the
syntax both for several literal types and for keyword arguments.  The snippet
illustrates both usages.

Other characters cause problems as well.  For example, adding to the load

----make code snip----
$(guile (append! %load-path (list "./")))
----make code snap----

For this snippet, I get "***missing separator.  Stop.".  I have to explicitly
show make that this is an assignment in order for it to be accepted:

----make code snip----
DUMMY:=$(guile (append! %load-path (list "./")))
----make code snap----

Looking at the parse function, it seems like all function calls are handled as
a variable assignment (possibly to nothing).  However, the manual shows
several non-assignment uses of the $(guile) function, so I assume that this is
meant to be supported behavior.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]