unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Alan Manuel Gloria <almkglor@gmail.com>
To: dwheeler@dwheeler.com
Cc: guile-devel@gnu.org
Subject: Re: Adding to guile curly-infix (SRFI 105), neoteric- & sweet-expressions
Date: Mon, 27 Aug 2012 12:30:03 +0800	[thread overview]
Message-ID: <CAF+kUQWa_BQjOLZGuafD5g1mMBG3TTo_2rvmciNwoypjwmic-w@mail.gmail.com> (raw)
In-Reply-To: <E1T5qkA-00080S-A3@fenris.runbox.com>

On Mon, Aug 27, 2012 at 12:16 PM, David A. Wheeler
<dwheeler@dwheeler.com> wrote:
> nalaginrut <nalaginrut@gmail.com>:
>> I ever port the sweet-expression as a language module for Guile, and I
>> have such an honor to say it's based on your work.
>> There're still some bugs I need to face. But it works fine already.
>> https://gitorious.org/nacre/guile-sweet
>
> Awesome!  Thanks!
>
> We've made some tweaks recently, though nothing that would invalidate existing code using it.  But now, for example, you can use f{- x} to mean (f (- x)).
>
>> Anyway, I'd like to see it becomes SRFIs. I've proposed it to be one of
>> official language module since there's multi-language feature in
>> Guile-2.x.
>> And it's more convenient to do that if we make sweet-expression the SRFIs.
>
> Agreed. We'll see how it goes.
>

Heya Nala Ginrut!

We noticed recently your effort in updating sweet-expressions to the
latest Guile.

We've also added support for some amount of attaching source locations
to read-in objects, and also indepedently updated it to work on recent
Guile 2.0.

I did much of the updating (at that time we had been unaware of your
work).  We did this by replacing the binding for 'read and
primitive-load on Guile, as it seemed to give the best coverage across
1.6, 1.8, and 2.0.

However, it leads to an edge case in Guile 2.0 where disabling
autocompilation leads to the module-loading C code path going through
a direct C call to the C implementation of primitive-load, a path that
only triggers if autocompilation disabled (when autocompilation is
enabled, it goes through a hook in the language support for Scheme,
which uses the 'read function we've rebound).

I had also considered adding support for sweet-expressions in a
language module for Guile, but this would require 2.0 (my own personal
needs mean that I need it to work way back in 1.6) , and I couldn't
figure out a way to tell Guile to start the REPL in sweet-expression
language (or any language other than Scheme for that matter).

Sincerely,
AmkG



  reply	other threads:[~2012-08-27  4:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-26 17:02 Adding to guile curly-infix (SRFI 105), neoteric- & sweet-expressions David A. Wheeler
2012-08-27  2:11 ` nalaginrut
2012-08-27  4:16   ` David A. Wheeler
2012-08-27  4:30     ` Alan Manuel Gloria [this message]
2012-08-28  2:57       ` Noah Lavine
2012-08-28  6:56         ` Alan Manuel Gloria
2012-08-27 11:20 ` Marijn
2012-09-01  3:16   ` David A. Wheeler
2012-08-28 20:43 ` Ludovic Courtès
2012-08-29  1:49   ` David A. Wheeler
2012-08-29  7:54     ` Alan Manuel Gloria

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=CAF+kUQWa_BQjOLZGuafD5g1mMBG3TTo_2rvmciNwoypjwmic-w@mail.gmail.com \
    --to=almkglor@gmail.com \
    --cc=dwheeler@dwheeler.com \
    --cc=guile-devel@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).