unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Source properties on arbitrary non-immediate values
Date: Tue, 11 Oct 2005 10:53:51 +0200	[thread overview]
Message-ID: <87ll10e8o0.fsf@laas.fr> (raw)
In-Reply-To: <87y8511fwo.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 10 Oct 2005 17:43:35 +0100")

Hi,

Neil Jerram <neil@ossau.uklinux.net> writes:

> That's fair enough.  I guess the rationale is that the unit of
> evaluation (as presented in backtraces for example) is a list, so it
> is useful for source properties to be stored on lists when those are
> read.

Sure.

> Yes, but why is that useful?

Why is it useless?  ;-)

I found it useful in a project that evaluates source in several steps:

  read [sexp] -> convert to alternate representation -> write things

Errors may occur during the last stage.  However, the user doesn't care
about the intermediate stage: they just want to know how the errors
occurring in the last stage relate to its source.  Therefore, source
information needs to be "piggy-backed" all along the process.

In any case, it's up to the user to decide what's useful and what's not.
Guile is here to implement mechanisms, not policy.  If we were to choose
the status-quo, then I'd have to implement a very similar mechanism by
myself, just because the one provided by Guile is unnecessarily
over-specific.

> (So far, I think I'd vote for fixing the manual rather than extending
> source properties ...)

I consider the restriction to pairs arbitrary (but I do understand that
it doesn't harm given the way it is currently used).  What's wrong with
removing such arbitrary restrictions?

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2005-10-11  8:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 12:23 [PATCH] Source properties on arbitrary non-immediate values Ludovic Courtès
2005-10-07 20:47 ` Kevin Ryde
2005-10-08 18:01   ` Neil Jerram
2005-10-10 12:10     ` Ludovic Courtès
2005-10-10 16:43       ` Neil Jerram
2005-10-11  8:53         ` Ludovic Courtès [this message]
2005-10-11 19:24           ` Neil Jerram
2005-10-12  8:42             ` Ludovic Courtès
2005-10-15 17:59               ` Neil Jerram
2005-10-15 18:36                 ` Neil Jerram
2005-10-17  8:08                   ` Ludovic Courtès
2005-10-10 21:24       ` Kevin Ryde
2005-10-11  8:43         ` 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=87ll10e8o0.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --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).