From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Christine Lemmer-Webber <cwebber@dustycloud.org>,
Chris Vine <vine35792468@gmail.com>,
guile-user@gnu.org
Subject: Re: Ideas for making Guile easier to approach
Date: Thu, 05 Oct 2023 16:15:12 +0200 [thread overview]
Message-ID: <8734ypjgfx.fsf@web.de> (raw)
In-Reply-To: <cab6f2db8f12acc3024d62a6c7e5ab08d189249a.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
Maxime Devos <maximedevos@telenet.be> writes:
> [[PGP Signed Part:No public key for 49E3EE22191725EE created at 2022-02-09T22:07:58+0100 using EDDSA]]
> Christine Lemmer-Webber schreef op wo 09-02-2022 om 10:18 [-0500]:
>> I'd like to actually see Guile integrate Wisp as a core language and
>> think about what it would be like to support it as a recommended
>> alternate way of writing programs. I think with the new block-level
>> highlighting that Arne has written, Wisp could be near ready for prime
>> time. This could mean:
>>
>> - Getting wisp actually in Guile's official languages
>> - Figuring out how to get geiser to be nicely integrated
>> - Figuring out how to make importing Wisp modules be as easy as
>> importing parenthetical-lisp ones
>
> I thought that Wisp = Scheme + a custom (non-parenthetical) reader,
> so I importing Wisp modules would work the same way as Guile modules I
> think?
>
> (use-modules (some wisp foo))
>
> AFAIK the only issue here is file extensions (mapping foo/bar.go to
> foo/bar.THE-FILE-EXTENSION-OF-WISP).
You can enable that via commandline flags to Guile, but you have to
precompile wisp files for that:
$ echo "define-module : foo
. #:export : bar
define : bar
. 'bar
" > foo.w
$ guild compile -f wisp foo.w
$ guile -L . -x .w
scheme@(guile-user)> (import (foo))
scheme@(guile-user)> (bar)
$1 = bar
This is not the most convenient of options, but it already provides a
way to actually ship wisp to people without them having to know about
it.
Aside: this is my header for wispwot:
#!/usr/bin/env bash
# -*- wisp -*-
exec -a "$0" ${GUILE:-guile} --language=wisp -x .w -L "$(dirname "$(realpath "$0")")" -C "$(dirname "$(realpath "$0")")" -e '(run-wispwot)' -c '' "$@"
; !#
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2023-10-05 14:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:19 Newbie thoughts on Guile Hall + Guix Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09 15:18 ` Ideas for making Guile easier to approach Christine Lemmer-Webber
2022-02-09 20:33 ` Daniel Tornabene
2022-02-09 21:05 ` Maxime Devos
2022-02-09 23:06 ` Keith Wright
2022-02-09 21:05 ` Olivier Dion via General Guile related discussions
2022-02-09 21:07 ` Maxime Devos
2023-10-05 14:15 ` Dr. Arne Babenhauserheide [this message]
2022-02-09 23:01 ` Chris Vine
2022-02-10 0:56 ` Timothy Sample
2022-02-10 10:01 ` Ricardo Wurmus
2022-02-10 1:32 ` Blake Shaw
2022-02-10 2:02 ` paul
2022-02-10 11:27 ` Mikael Djurfeldt
2022-02-10 14:34 ` Leo Butler
2022-02-10 15:58 ` Mikael Djurfeldt
2022-02-10 18:25 ` Olivier Dion via General Guile related discussions
2023-09-27 19:29 ` Christine Lemmer-Webber
2023-09-28 12:30 ` Maxime Devos
2022-02-09 6:28 ` Newbie thoughts on Guile Hall + Guix Catonano
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=8734ypjgfx.fsf@web.de \
--to=arne_bab@web.de \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
--cc=vine35792468@gmail.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).