Achim Gratz <strom...@nexgo.de> writes: > Aaron Ecay writes: >> In order for the cache feature to work, the hash of a finished >> computation must be inserted. But, this is not currently done for src >> blocks which have the option :results none. Thus, we should insert a >> dummy empty result for these blocks, which will hold the hash. > > Getting a results block when specifying ":results none" feels a bit > strange.
I would agree. I don't believe *any* changes should take place in the buffer when a code block is executed with ":results none". > Since it is not the results that are hashed, but the effective > parameters of the invocation, wouldn't it make more sense to store the > parameter hash with the source block or call rather than the result? > That would free up the current place to hash the actual result to > check if the results have been tampered with. > I prefer leaving the hash with the results, as it is the results which are "hashed". Also, same input does not always guarantee same output, e.g., #+begin_src sh date #+end_src > > > Regards, > Achim. -- Eric Schulte http://cs.unm.edu/~eschulte
