From: Marc Chantreux <mc@unistra.fr>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: CToID <funk443@yandex.com>, guile-user@gnu.org
Subject: Re: Is it possible to write program only in Guile?
Date: Wed, 18 Oct 2023 15:32:20 +0200 [thread overview]
Message-ID: <ZS_eZHkl_FLa0EFY@prometheus> (raw)
In-Reply-To: <87fs289iu6.fsf@laura>
hi,
I don't get the difference between this
> 2. The program is written in Guile. It can access C routines with the
> foreign function interface (FFI). …
and this:
> There is a third way that I personally use. I use the FFI to make
> bindings of the public interface of a low-level C library I work on.
i choose the strategy 2 using the shebang described here
https://www.gnu.org/software/guile/manual/html_node/Running-Guile-Scripts.html
the only annoyance I have occurs the first time a user runs the script:
he gets this message
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
would be nice to have a flag to handle it the other way
#!/usr/local/bin/guile -s --silent-auto-compilation
!#
Did I miss something?
regards,
marc
next prev parent reply other threads:[~2023-10-18 13:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 10:23 Is it possible to write program only in Guile? CToID
2023-10-18 12:51 ` Basile Starynkevitch
2023-10-18 13:31 ` CToID
2023-10-18 13:36 ` Basile Starynkevitch
2023-10-18 14:43 ` Greg Troxel
2023-10-18 15:06 ` CToID
2023-10-18 15:50 ` Hans Åberg
2023-10-18 20:24 ` Janneke Nieuwenhuizen
2023-10-18 16:11 ` Thompson, David
2023-10-19 4:52 ` tomas
2023-10-19 11:18 ` wolf
2023-10-20 4:35 ` tomas
2023-10-18 13:10 ` Olivier Dion
2023-10-18 13:32 ` Marc Chantreux [this message]
2023-10-18 13:44 ` Olivier Dion
2023-10-18 18:49 ` wolf
2023-10-18 19:14 ` Olivier Dion
2023-10-20 10:19 ` Marc Chantreux
2023-10-18 13:12 ` Zelphir Kaltstahl
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=ZS_eZHkl_FLa0EFY@prometheus \
--to=mc@unistra.fr \
--cc=funk443@yandex.com \
--cc=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).