Re: Gnus always loads cl

[Katsumi@Yamaoka.cc]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 1447 bytes --]

Hi, I am the same as that of Katsumi Yamaoka <yamaoka@jpl.org>. :)

>>>>> In <87hefnu7sn.fsf@crybaby.cs.uni-dortmund.de> 
>>>>>	Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Gro^[.A^[N_johann) wrote:

>> (unless (and (fboundp 'gethash) (fboundp 'hash-table-count)
>> 	     (fboundp 'make-hash-table) (fboundp 'mapc)
>> 	     (fboundp 'puthash))
>>   (require 'cl)
>>   (unless (fboundp 'puthash)
>>     (defalias 'puthash 'cl-puthash)))
>>
>> However, if such a thing is required, my will inclines to
>> forsake Emacs 20 users.  Do you have any other ideas?

Kai> Why forsake Emacs 20 users?  The code is not that terrible :-)

Since I'm not using Emacs 20 usually, I come to feel it
troublesome.  But we cannot forsake Meadow users. ;-)

Kai> And then, maybe it's sufficient to test some of those functions
Kai> instead of all of them -- we expect them to be defined in the same
Kai> file anyway, right?

I make an issue of only cl run-time functions and I graspe all
of them.  Which function do you think we can remove from a
subject of examination?  I don't know.

By the way, I've made gnus-clfns.el in T-gnus (which is base on
Oort Gnus, using FLIM and SEMI for MIME functions, using APEL
to support Mule 19.34 as well as Emacs 20/21).  That file
provides compiler macros for cl run-time functions as it is done
by dgnushack.el in Oort Gnus.  If such demand increases, we
should probably do the same thing also in Oort Gnus.
-- 
Katsumi@Yamaoka.cc