From: Andy Wingo <wingo@pobox.com>
To: "Tommi Höynälänmaa" <tommi.hoynalanmaa@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Source properties and the unexpanded source code
Date: Thu, 04 Aug 2016 23:08:37 +0200 [thread overview]
Message-ID: <87invgs0mi.fsf@pobox.com> (raw)
In-Reply-To: <CAAkPRiyW19ghQXJHoQrNjV4qQJY8vdW0gbsyHYo2BgLFcO6tOA@mail.gmail.com> ("Tommi Höynälänmaa"'s message of "Mon, 25 Jul 2016 14:08:29 +0300")
On Mon 25 Jul 2016 13:08, Tommi Höynälänmaa <tommi.hoynalanmaa@gmail.com> writes:
> Is it possible to access unexpanded source code information from the
> expanded source code in psyntax.scm? When I look at the source
> properties given to the build-xxx procedures there is only line
> number, column number, and filename.
Sadly this is all there is. If you have an idea as to what we could
provide, we're all ears :) Racket is usually a good inspiration here.
Andy
prev parent reply other threads:[~2016-08-04 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 11:08 Source properties and the unexpanded source code Tommi Höynälänmaa
2016-08-04 21:08 ` Andy Wingo [this message]
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=87invgs0mi.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=tommi.hoynalanmaa@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).