[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] compilation issues of new export framework
From: |
Nicolas Goaziou |
Subject: |
Re: [O] compilation issues of new export framework |
Date: |
Sat, 09 Feb 2013 18:50:39 +0100 |
Hello,
Achim Gratz <address@hidden> writes:
> an oddity occurs since the new exporter moved into core (I don't think I
> had seen this before, so maybe you can relate to what is different now):
>
> Compiling /lisp/org-mode/lisp/org.el...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
> Loading org-element...
Yes, I noticed this one too, but I don't know yet from where it could
come from.
> This only happens when using byte-recompile-directory, which means
> org-element has already been loaded in that session and is present as a
> byte-compiled file. I haven't yet found where in org.el these loads are
> triggered, but it seems that this might be related to macro expansion.
> In any case, the resulting org.elc file therefore depends on the
> compilation method, which is highly undesirable. I haven't been able to
> analyse this further.
>
> Another sticky point is your use of declare-function: some of these are
> actually defsubst, not defun:
>
> org-element-{contents,nested-p,element-property,put-property}
>
> I don't think they will be inlined unless their definition has been
> interned, declaration alone will not suffice.
I don't know either how inline functions behave in this situation.
> I don't see an easy way to factor out those parts from org-element
> that are needed by org, but I suggest that we should find one.
It is always possible to make them regular functions. Some profiling may
be necessary, though.
> There are more errors when doing a "make ORGCM=slint2 compile" in the
> last pass. These files are probably all just missing an
>
> (eval-when-compile (require 'cl))
>
> but I only checked ox-md.
Indeed. Fixed. Thank you.
Regards,
--
Nicolas Goaziou
- Re: [O] [ANN] Merge of new export framework on Wednesday, (continued)
Re: [O] [ANN] Merge of new export framework on Wednesday, Achim Gratz, 2013/02/09
Re: [O] [ANN] Merge of new export framework on Wednesday, Jambunathan K, 2013/02/09
Re: [O] compilation issues of new export framework, Achim Gratz, 2013/02/09
- Re: [O] compilation issues of new export framework,
Nicolas Goaziou <=
- Re: [O] compilation issues of new export framework, Achim Gratz, 2013/02/09
- Re: [O] compilation issues of new export framework, Achim Gratz, 2013/02/10
- Re: [O] compilation issues of new export framework, Nicolas Goaziou, 2013/02/10
- Re: [O] compilation issues of new export framework, Nicolas Goaziou, 2013/02/10
- Re: [O] compilation issues of new export framework, Achim Gratz, 2013/02/11
- Re: [O] compilation issues of new export framework, Nicolas Goaziou, 2013/02/11
- Re: [O] compilation issues of new export framework, Achim Gratz, 2013/02/11