Re: Permanently fix org versioning breakage during builds?

[Ihor Radchenko <yantar92@posteo.net>]

João Távora <joaotavora@gmail.com> writes:

>> 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.

I do not think that your idea will work.
What you propose is compiling `org-assert-version' once.
However, the whole point behind `org-assert-version' is that it should
be compiled into every .elc file in Org:

   (equal (org-release) ,(org-release))

will only work when ,(org-release) is expanded at compile file thus
recording the Org version used during the compilation inside the
resulting .elc file. This way, we can compare Org version active in
Emacs session vs. Org version used for the compilation.

> 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.

May you please try to explain what you mean in other words? I am not
sure what you are trying to convey in this paragraph.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>