From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Babel] [Bug] Cache
Date: Fri, 06 Dec 2013 21:04:48 +0100 [thread overview]
Message-ID: <86txeln3tr.fsf@somewhere.org> (raw)
In-Reply-To: 87k3fhkb1c.fsf@Rainer.invalid
Achim Gratz wrote:
> Eric Schulte writes:
>> In that thread we agreed that the expansion of no-web references
>> *should* be included in code blocks for hashing, but no-one has had the
>> time to implement this.
>
> I think we may have discussed this before, but if you make the hashes
> dependent on the possibly recursive noweb expansions this would require
> that all expansions be re-computed all the time
I did not think at recursive Noweb expansions. But, yes, that problem could
come up as well.
> or you would need to discern which of the expansions are "pure" (i.e. depend
> only on their arguments, functional-style), which have session semantics and
> which of the ones that have session semantics should possibly not be
> re-evaluated. I'm not sure that opening this can of worms is worth the
> trouble.
Maybe a solution to avoid recomputing too much things (in number, and in taken
time to do that) would be to only compute the hash for "static" expansions --
the ones without parameters, where it's simply a copy/paste of text in multiple
spots.
If even that is not done/doable, then some error should be triggered when one
uses both the "cache" and the "noweb" header arguments. Because, in the current
situation, we think that the graphs (or, in a general way, the results) are
up-to-date while it's wrong -- you've changed some piece of code somewhere, and
the cached results are still used.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-12-06 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 11:13 [Babel] [Bug] Cache Sebastien Vauban
2013-11-22 15:03 ` Eric Schulte
2013-12-02 15:46 ` Sebastien Vauban
2013-12-06 19:15 ` Eric Schulte
2013-12-06 19:57 ` Achim Gratz
2013-12-06 20:04 ` Sebastien Vauban [this message]
2013-12-07 2:29 ` Eric Schulte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86txeln3tr.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.