GNU bug report logs - #22884
25.0.92; C/l mode editing takes waaaayy too long

Previous Next

Full log

Message #19 received at 22884 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: eggert <at> cs.ucla.edu, 22884 <at> debbugs.gnu.org
Subject: Re: 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 <at> muc.de>
> Cc: 22884 <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.