[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22884: 25.0.92; C/l mode editing takes waaaayy too long
From: |
Eli Zaretskii |
Subject: |
bug#22884: 25.0.92; C/l mode editing takes waaaayy too long |
Date: |
Thu, 03 Mar 2016 22:38:36 +0200 |
> Date: Thu, 3 Mar 2016 19:23:30 +0000
> From: Alan Mackenzie <acm@muc.de>
> Cc: 22884@debbugs.gnu.org
>
> OK. Could you give me a clue as to what they mean, please? For
> example, in
>
> INLINE EMACS_INT
> (XLI) (Lisp_Object o)
> {
> return lisp_h_XLI (o);
> }
>
> , what does "(XLI)" do?
It's an age-old method of calling a function without risking it being
shadowed by a macro, AFAIK.
> It can't be an expansion of the CPP macro "XLI", surely, lacking, as
> it does, an argument.
Exactly. And that's why it ensures a function will be called instead
of the macro.
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Paul Eggert, 2016/03/02
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Alan Mackenzie, 2016/03/03
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Eli Zaretskii, 2016/03/03
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Paul Eggert, 2016/03/03
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Alan Mackenzie, 2016/03/04
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Paul Eggert, 2016/03/04
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Alan Mackenzie, 2016/03/04
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Alan Mackenzie, 2016/03/13
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Alan Mackenzie, 2016/03/08
- bug#22884: 25.0.92; C/l mode editing takes waaaayy too long, Paul Eggert, 2016/03/09