[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should we just start dumping cl-lib?
From: |
Mark Oteiza |
Subject: |
Re: Should we just start dumping cl-lib? |
Date: |
Fri, 2 Oct 2015 10:22:40 -0400 |
User-agent: |
Mutt/1.5.24+19 (9de2f1c6da87) (2015-08-30) |
On 02/10/15 at 05:18pm, Eli Zaretskii wrote:
> > Date: Fri, 2 Oct 2015 10:14:52 -0400
> > From: Mark Oteiza <address@hidden>
> > Cc: address@hidden
> >
> > Regarding the breakage with winner.el, I don't understand why under some
> > circumstances nothing seems to break if cl- functions are used at
> > runtime in things with only `(eval-when-compile (require 'cl-lib))`. For
> > instance, git-grepping for 'cl-remove-if' I see package.el and
> > checkdoc.el don't require cl-lib at runtime.
>
> Are the cl-lib functions they use auto-loaded, perhaps?
Yes. However, it was an issue in winner.el--why not in these libraries?
- Re: Should we just start dumping cl-lib?, (continued)
- Re: Should we just start dumping cl-lib?, John Wiegley, 2015/10/08
- Re: Should we just start dumping cl-lib?, Daniel Colascione, 2015/10/08
- Re: Should we just start dumping cl-lib?, Eli Zaretskii, 2015/10/08
- Re: Should we just start dumping cl-lib?, Daniel Colascione, 2015/10/08
- Re: Should we just start dumping cl-lib?, Eli Zaretskii, 2015/10/08