[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Correct byte compiler error/warning positions. The solution!
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Correct byte compiler error/warning positions. The solution! |
|
Date: |
Sat, 27 Nov 2021 07:53:36 +0200 |
> Date: Fri, 26 Nov 2021 19:56:21 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> A _LOT_ of these comparisons were for NILP, which is just #defined as EQ
> (arg, Qnil). However if NILP were to be defined directly as arg ==
> Qnil, it would bypass the overhead in EQ.
How can you use == when the operands could be structures?
- Correct byte compiler error/warning positions. The solution!, Alan Mackenzie, 2021/11/26
- Re: Correct byte compiler error/warning positions. The solution!,
Eli Zaretskii <=
- Re: Correct byte compiler error/warning positions. The solution!, Alan Mackenzie, 2021/11/27
- Re: Correct byte compiler error/warning positions. The solution!, Eli Zaretskii, 2021/11/27
- Re: Correct byte compiler error/warning positions. The solution!, Alan Mackenzie, 2021/11/27
- Re: Correct byte compiler error/warning positions. The solution!, Eli Zaretskii, 2021/11/27
- Re: Correct byte compiler error/warning positions. The solution!, Alan Mackenzie, 2021/11/27
- Re: Correct byte compiler error/warning positions. The solution!, Eli Zaretskii, 2021/11/28
- Re: Correct byte compiler error/warning positions. The solution!, Alan Mackenzie, 2021/11/29
- Re: Correct byte compiler error/warning positions. The solution!, Eli Zaretskii, 2021/11/29
- Re: Correct byte compiler error/warning positions. The solution!, Alan Mackenzie, 2021/11/29
- Re: Correct byte compiler error/warning positions. The solution!, Robert Pluim, 2021/11/29