Pete Ware <ware(a)pc-786a.cis.ohio-state.edu> writes:
> Before coding systems came into the picture, Fmd5 was an
exemplary
> of Lisp elegance:
>
> `md5' is a built-in function
> (md5 OBJECT &optional START END)
>
> Documentation:
> Return the MD5 message digest of OBJECT, a buffer or string.
>
> Optional arguments START and END denote positions for computing the
> digest of a portion of OBJECT.
I'm a MOLE (MOnoLingual Emacs) so take what I have with a shalt shaker
but shouldn't OBJECT be in the already appropriate coding system for
whatever the message digest is being computed?
Nope. OBJECT is a buffer or string in internal XEmacs format, and we
don't want to calculate a digest of the internal representation
(that's what the old non-Mule-ized code did), but of the external
representation, as saved to disk etc.
To put it another way, shouldn't there be a set of functions
that
given an OBJECT in one coding system return another OBJECT in a
different coding system?
It would be very wasteful, I think.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
- Now what did we learn from this?
- I learned what my liver looks like!