From: silas poulson <silas8642@hotmail.co.uk>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Can guile be implementation independent?
Date: Fri, 17 Dec 2021 13:32:01 +0000 [thread overview]
Message-ID: <6FF9A1D9-749B-4BA4-8FA1-8EBF751D9FB6@hotmail.co.uk> (raw)
In-Reply-To: <dd4fea80-bb8e-9f54-f3f6-36d952c14dc1@rixotstudio.cz>
Uncertain if anymore but Guile provides list of r7rs incompatiblities
here
<https://www.gnu.org/software/guile/manual/html_node/R7RS-Incompatibilities.html>
Silas
> On 17 Dec 2021, at 03:01, Jacob Hrbek <kreyren@rixotstudio.cz> wrote:
>
> Looks interesting, are there any known limitations in relation to Guile?
>
> On 12/17/21 03:53, Nala Ginrut wrote:
>> Hi Jacob!
>> You may take a look at akku.scm
>> You can write r7rs code and use Guile as one of the compiler alternatives.
>>
>> Best regards.
>>
>>
>> On Fri, Dec 17, 2021, 09:43 Jacob Hrbek <kreyren@rixotstudio.cz> wrote:
>>
>> I am used to working with common lisp where i can write code that is
>> "implementation independent" meaning that following a specific coding
>> style makes it compatible across multiple interpretators/compilers
>> (sbcl, LispWorks, etc..)
>>
>> Is there a way to do the same on GNU Guile? Like writing a code
>> that can
>> be interpreted by implementations that are following the IEEE
>> 1178-2008
>> or R7RS standard?
>>
>> -- Jacob Hrbek
>>
> --
> -- Jacob Hrbek
> <publickey - kreyren@rixotstudio.cz - 1677db82.asc>
next prev parent reply other threads:[~2021-12-17 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 1:42 Can guile be implementation independent? Jacob Hrbek
2021-12-17 2:53 ` Nala Ginrut
2021-12-17 3:01 ` Jacob Hrbek
2021-12-17 3:27 ` Nala Ginrut
2021-12-17 13:32 ` silas poulson [this message]
2021-12-17 16:26 ` Dr. Arne Babenhauserheide
2021-12-18 15:30 ` Tim Van den Langenbergh
2021-12-18 18:47 ` Dr. Arne Babenhauserheide
2021-12-17 16:19 ` Maxime Devos
2021-12-17 17:05 ` [EXT] " Thompson, David
2021-12-18 17:10 ` Taylan Kammer
2021-12-19 20:03 ` Keith Wright
2021-12-19 20:57 ` Taylan Kammer
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=6FF9A1D9-749B-4BA4-8FA1-8EBF751D9FB6@hotmail.co.uk \
--to=silas8642@hotmail.co.uk \
--cc=guile-user@gnu.org \
--cc=kreyren@rixotstudio.cz \
/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).