Re: Permanently fix org versioning breakage during builds?

["João Távora" <joaotavora@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

LOn Sat, Dec 23, 2023, 18:03 Ihor Radchenko <yantar92@posteo.net> wrote:

> João Távora <joaotavora@gmail.com> writes:
>
> > Another way to fix this issue is for the org developers to not deal with
> > macro expansion-site recompilation problems so aggressively, and making
> > more use of the "call-with" idiom whereby a macro immediately expands to
> a
> > function that has all the frequently-changing implementation details.
>
> May you elaborate?
>

I have already elaborated a while back, but on a tangent deep down in a
thread and I'm on my phone right now. So maybe these links would give you
an idea of what it looks like.

http://random-state.net/log/3390120648.html
https://www.reddit.com/r/Common_Lisp/comments/okvgf0/examples_of_callwith_style_in_macros/
https://news.ycombinator.com/item?id=12476032

These are all common lisp related, but there are, I'm fairly sure, numerous
examples in Elisp, though not necessarily named "call-with". Let me know
what you understand of the examples before we continue.

You may also want to elaborate yourself on an example of a macro that is
emblematic of the expansion-site recompilation problem that, as I contend,
you fixed somewhat heavy-handedly and lead to these recurring irritations
to many users. We can see if we can fix that example with with the
technique I allude to.

João

[-- Attachment #2: Type: text/html, Size: 2417 bytes --]