From: Sunjoong Lee <sunjoong@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: guile-user@gnu.org
Subject: Re: SRFI-64 implementation for Guile 2.0
Date: Mon, 16 Apr 2012 05:35:10 +0900 [thread overview]
Message-ID: <CAK93xho45Bx21de4=pOt-fdqf0Tp4RLwamsgeMzSMmgdiMz1dQ@mail.gmail.com> (raw)
In-Reply-To: <CAK93xhpCz-tRYm4oypjKrCme4UbkFeJ8XVx4pL0p5K65NiBF2w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1381 bytes --]
Now, srfi-64.scm works on Guile 1.8 and 2.0.
There are two different thins;
1) Guile 1.8 does not support nested block comments.
So, it does not pass srfi-64-test.scm test suite.
But, comments are comments - not problem.
2) srfi-64.scm on Guile 2.0 can catch and report the source form
like this;
source-file: "srfi-64-test.scm"
source-line: 129
source-form: (test-equal "1.1.1. Very simple" (quote (("a") ("b") ()
() () (1 1 0 0 0))) (t))
srfi-64.scm on Guile 1.8 does not support it yet
because I'm a newbie of scheme and don't understand Guile yet.
I hope someone fix these problems;
a) On Guile 2.0, I used (datum->syntax form (syntax->datum form))
b) On Guile 2.0, I used (assq-ref (syntax-source form) 'filename)
2012/4/14 Sunjoong Lee <sunjoong@gmail.com>
>
> 2012/4/14 Per Bothner <per@bothner.com>
>
>> This is nice. It would be great if the Guile port would be merged
>> into the reference implementation, presumably using cond-expand.
>> That way bug-fixes or changes in one could be more easily be
>> merged into the other.
>
>
Now, srfi-64.scm works on Chicken 4.7.
Per Bothner adviced me it's better to merge it into the reference
implementation.
I was not convinced to check right merge.
So, I ported it for Chicken 4.7 and Guile 1.8 - it works now.
Right merge? I'm not sure yet but hope so.
[-- Attachment #1.2: Type: text/html, Size: 2248 bytes --]
[-- Attachment #2: srfi-64.scm.gz --]
[-- Type: application/x-gzip, Size: 8101 bytes --]
next prev parent reply other threads:[~2012-04-15 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 21:53 SRFI-64 implementation for Guile 2.0 Sunjoong Lee
2012-04-14 1:39 ` Sunjoong Lee
2012-04-14 2:06 ` Per Bothner
2012-04-14 12:43 ` Sunjoong Lee
2012-04-15 20:35 ` Sunjoong Lee [this message]
2012-04-20 2:50 ` Noah Lavine
2012-04-20 4:21 ` Per Bothner
2012-04-20 10:19 ` Sunjoong Lee
2012-04-20 18:27 ` Per Bothner
2012-04-20 20:53 ` Sunjoong Lee
2012-04-20 15:18 ` Ludovic Courtès
2012-04-20 17:36 ` Sunjoong Lee
2012-04-21 23:08 ` Ludovic Courtès
2012-04-23 6:07 ` Sunjoong Lee
2012-12-28 3:22 ` Per Bothner
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='CAK93xho45Bx21de4=pOt-fdqf0Tp4RLwamsgeMzSMmgdiMz1dQ@mail.gmail.com' \
--to=sunjoong@gmail.com \
--cc=guile-user@gnu.org \
--cc=per@bothner.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).