unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: source-location->source-properties
Date: Sat, 20 Nov 2010 23:15:27 +0100	[thread overview]
Message-ID: <m3mxp3zlog.fsf@unquote.localdomain> (raw)
In-Reply-To: <8739qyz534.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 18 Nov 2010 22:37:03 +0100")

Hello :)

On Thu 18 Nov 2010 22:37, ludo@gnu.org (Ludovic Courtès) writes:

> Hi!

Hey I'm caught up to this week! :)

> "Andy Wingo" <wingo@pobox.com> writes:
>
>> +            source-location->source-properties
>
> I was thinking that this procedure could be made internal to the ES
> compiler, so that the export list of (system base lalr) remains
> identical to that upstream.

Well, we could. It just seemed like something other compiler writers
might want, so I put it here. Is it important that we have exactly the
same set of exports as upstream, or is a compatible set sufficient?

I'm happy to move it, but I would like to come to some shared
understanding of how to deal with external projects in Guile.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-11-20 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1877026923.880808.1290087063603.JavaMail.root@zmbs1.inria.fr>
2010-11-18 21:37 ` source-location->source-properties Ludovic Courtès
2010-11-20 22:15   ` Andy Wingo [this message]
2010-11-21 22:44     ` source-location->source-properties Ludovic Courtès

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=m3mxp3zlog.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).