Stephen Leake <[EMAIL PROTECTED]> writes:

> Michael Olson <[EMAIL PROTECTED]> writes:
>
>> I'm fairly certain that CL.el does not have any sort of union structure.
>
> Ok.
>
>> And even if it did, we would not want to use it if it would
>> introduce a dependency on cl at run time (since RMS does not want
>> code to (require 'cl)). It would probably be best just to leave that
>> particular part of the structure unchanged.
>
> I think it's too late for that. At least for the xmtn back-end; it
> uses cl runtime extensively.

Other back-ends are very carefull not to use it at runtime.

Indeed, most of cl.el is just macros, and do not need to be loaded at
runtime.

> grepping dvc/lisp shows that tla-core and tla-defs also have "require
> 'cl" not inside "eval-when-compile". 

Look more carefully (hint: grep -C to get the context) ;-).

> RMS is stepping down as Emacs maintainer (sometime; I'm not reading
> the emacs-devel list anymore, so I don't know if it has actually
> happened yet).

That's not just RMS I think.

> If the argument is "cl is slow" then the response is "it's fast enough
> for 90% of users" combined with "getting it right is more important
> than making it really fast".

I believe the main argument is namespace pollution. Last time I heard
about it, the answer was roughly "everybody thinks native common lisp
rocks, but everybody agrees it sucks through an emulation layer in
Emacs". I personnally don't have a really strong opinion on that, but
we removed the runtime 'cl dependancy after several user complaints.

> If this is is a problem, I could go back to using cond instead of
> ecase. I'm not clear if defstruct requires cl runtime; how do I tell?

,----[ C-h f ecase RET ]
| ecase is a Lisp macro in ...
|            ^^^^^^^^^^
| [back]
`----

,----[ C-h f defstruct RET ]
| defstruct is a Lisp macro in ...
|                ^^^^^^^^^^
| [back]
`----

Up to now, there's no _runtime_ dependancy. Good news ;-).

-- 
Matthieu

_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev

Reply via email to