On 09/11/15 21:04, Achim Gratz wrote:
John Wiegley writes:
You will find that the argument really wasn't about performance, but
complexity.
I can accept a complexity argument,
I meant O() complexity, not implementation complexity.
if my request were really "a separate
code-path". I'm not sure it is. For example, my needs could be satisfied by
something as simple as:
(defun parse-org-entry (...)
(let ((props (funcall 'parse-org-properties-function ...)))
...))
`parse-org-properties-function' would point to a function that does what Org
8.3 does now. This gives me the option of porting over the 8.2 version and
keeping the old behavior. All that needs to be done is to allow this hook, no?
If it's not about providing the alternative behaviour within Org, then
what does this allow you to do that advising parse-org-entry can't? A
hook still has the cost of simply being there even when I don't use it.
John, if you end up writing an advice for this function, please share it
with the list, as I would like the 8.2 behavior as well (I unfortunately
don't know enough elisp and org internals to do such a thing).
Thanks!
S.
