Re: CL package suggestion

[Ilya Shlyakhter <ilya_shl@alum.mit.edu>]

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

So, about the cl package:

If remove-if is renamed cl-remove-if and then 'remove-if defaliased to
'cl-remove-if,
is it now ok to (require 'cl) at runtime?  Won't the alias now conflict
with whatever
definition of remove-if the user had?
And if you don't (require 'cl) at runtime, then you can't call cl-remove-if
at runtime,
since it might not be available.

One could move cl-remove-if etc into a separate module called cl-funcs,
so if you want to call cl-remove-if at runtime you (require 'cl-funcs).
This would somewhat break up the logical structure of the cl package,
since things will get grouped by whether they're functions or macros rather
than by topic.

Suggestions?

On Wed, Apr 4, 2012 at 9:06 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:

> > Agree about cl- being better than ecl- .
> > Btw, if remove-if becomes defalias'ed to cl-remove-if, aren't the two
> calls
> > indistinguishable to the byte compiler?
>
> The name is different, so the compiler can definitely tell the difference.
>
> > If they are, and calling cl-remove wouldn't trigger a warning,
> > wouldn't remove-if calls also become warning-less?
>
> Not necessarily, no.
>
>
>        Stefan
>

[-- Attachment #2: Type: text/html, Size: 1786 bytes --]