unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: tomas@tuxteam.de
To: Damien Mattei <damien.mattei@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: inserting a file in a module?
Date: Fri, 6 Oct 2023 09:52:44 +0200	[thread overview]
Message-ID: <ZR+8zATCFjddyzLN@tuxteam.de> (raw)
In-Reply-To: <CADEOadcC2FSbK9dZjjNQcw76a3SYctSG2cjmXLK4p+3snHGrLQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

On Fri, Oct 06, 2023 at 09:14:50AM +0200, Damien Mattei wrote:
> On Thu, Oct 5, 2023 at 9:35 AM <tomas@tuxteam.de> wrote:
> 
> > I don't know whether it is TRT, but you might try wrapping your
> > define form in (eval-when (compile) ...) or similar.
> i tried this:
> (eval-when (compile) (define scheme-plus-path
> "/Users/mattei/Dropbox/git/Scheme-PLUS-for-Guile"))
> 
> (include (string-append scheme-plus-path "/" "Scheme+.scm"))
> 
> but still have the error:
> In procedure string-prefix?: Wrong type argument in position 2
> (expecting string): (string-append scheme-plus-path "/" "Scheme+.scm")

Interesting. Even with the shotgun approach

  (eval-when (expand load eval compile)
    ...)

include isn't seeing a value for the defined variable. My hunch is now
that the define itself is special. There's some note in the docs about
that, but I'm ATM at $DAYJOB and not supposed to be doing this :)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-10-06  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  6:39 inserting a file in a module? Damien Mattei
2023-10-05  7:34 ` tomas
2023-10-05  9:12   ` Damien Mattei
2023-10-06  7:14   ` Damien Mattei
2023-10-06  7:52     ` tomas [this message]

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=ZR+8zATCFjddyzLN@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=damien.mattei@gmail.com \
    --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).