unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Sam Lee" <samlee746@yahoo.com>, 52218@debbugs.gnu.org
Subject: bug#52218: Unable to define more than one R7RS library per file
Date: Wed, 01 Dec 2021 11:00:46 +0100	[thread overview]
Message-ID: <aebc490c-621c-4e2a-b232-19c0809e1f59@www.fastmail.com> (raw)
In-Reply-To: <20211201074553.bzuoffwpaxw3da44@localhost>

Hi Sam!

I am not a maintainer , nor a very proficient guile hacker, but I do have some input.

This is in line with the limitations of guile's R6RS implementation. I think this is a long standing, low priority bug. It has to do with the expansion of library (or define-library in this case) not properly resetting the current module. 

In the manual there is a section called "R6RS incompatibilities" that mentions this. Maybe an "R7RS incompatibilities" should be added.


Best regards
  Linus Björnstam

On Wed, 1 Dec 2021, at 08:45, Sam Lee via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote:
> Guile is unable to handle more than one define-library per file. For
> example, this is "mylibs.sld", which contains two define-library:
>
> (define-library (example mylib)
>   (import (scheme base))
>   (export f)
>   (begin
>     (define (f x)
>       (+ x 1))))
>
> (define-library (example main)
>   (import (scheme base)
>           (scheme write)
>           (example mylib))
>   (export main)
>   (begin
>     (define (main)
>       (display "The answer is: ")
>       (display (f 1))
>       (newline))))
>
>
> When loading this file into Guile using "guile -l mylibs.sld", or by
> using (load "mylibs.sld"), Guile will show this error:
>
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;;       or pass the --no-auto-compile argument to disable.
> ;;; compiling /home/user/mylibs.sld
> ;;; WARNING: compilation of /home/user/mylibs.sld failed:
> ;;; Syntax error:
> ;;; unknown location: definition in expression context, where 
> definitions are not allowed, in form (define (main) (display "The 
> answer is: ") (display (f 1)) (newline))
> ice-9/psyntax.scm:2794:12: In procedure syntax-violation:
> Syntax error:
> /home/user/mylibs.sld:14:4: definition in expression context, where 
> definitions are not allowed, in form (define (main) (display "The 
> answer is: ") (display (f 1)) (newline))
>
>
> The error is always caused by the second define-library. Apparently,
> Guile no longer understands that define-library is a special form by the
> time the second define-library is evaluated. Is it not possible to
> define two R7RS libraries in the same file?
>
> Guile version: 3.0.7





  reply	other threads:[~2021-12-01 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211201074553.bzuoffwpaxw3da44.ref@localhost>
2021-12-01  7:45 ` bug#52218: Unable to define more than one R7RS library per file Sam Lee via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-12-01 10:00   ` Linus Björnstam [this message]
2021-12-02  2:55     ` Sam Lee via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-12-03 14:20       ` Linus Björnstam

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=aebc490c-621c-4e2a-b232-19c0809e1f59@www.fastmail.com \
    --to=linus.bjornstam@veryfast.biz \
    --cc=52218@debbugs.gnu.org \
    --cc=samlee746@yahoo.com \
    /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).