Code review - Issue 547920045: define-markup-command-internal -> module-define-markup-command!https://codereview.appspot.com/2020-05-08T17:30:10+00:00rietveld
Message from unknown
2020-04-12T12:58:13+00:00dakurn:md5:b7b99c98fa97e127b135b84b2f1e32f3
Message from hanwenn@gmail.com
2020-05-08T17:12:41+00:00hanwennurn:md5:0b1f784a6bb73148d4c15a639bfd26cf
I don't understand how this approach could ever help byte-compiling the markup scheme files. This still uses module-define! , so the guile2 compilation step will be oblivious to markup functions.
Message from dak@gnu.org
2020-05-08T17:30:10+00:00dakurn:md5:5a5d31f7d802c8fe3c3dba808097894a
On 2020/05/08 17:12:41, hanwenn wrote:
> I don't understand how this approach could ever help byte-compiling the markup
> scheme files. This still uses module-define! , so the guile2 compilation step
> will be oblivious to markup functions.
It makes it easier to create specific different behavior for byte-compilation using eval-when.