Re: [PATCH] Unicode Lisp reader escapes

[Oliver Scholz]

Aidan Kehoe <address@hidden> writes:

>  Ar an cúigiú lá de mí Bealtaine, scríobh Oliver Scholz>: 
>
>  > >  > What happens when a Lisp file is byte-compiled--do we want the result
>  > >  > to depend on the local settings?
>  >
>  > [...]
>  >
>  > > It does currently, to the extent of local settings preventing successful
>  > > compilation. Cf. this code (on Unix):
>  > 
>  > [...]
>  > >     (insert (concat
>  > >       ";; -*- coding: utf-8 -*-\n\n"
>  > >       "(require 'cl)\n\n"
>  > >       "(defun describe-our-string ()\n"
>  > >       "  (let ((our-char ?"
>  > >       (format "%c%c%c" ?\345 ?\215 ?\227)
>  > [...]
>  > >   (utf-translate-cjk-mode 0)
>  > [...]
>  > >   (byte-compile-file our-test-file-name)
>  > [...]
>  > 
>  > I am afraid that is not relevant here. This just tells Emacs to not
>  > deal with UTF-8 encoded CJK characters and then tell it to deal with
>  > such an character.
>
> It byte compiles a file, changes a local setting, and byte-compiles the file
> again with a different result. That is relevant to Eli’s question. 

Sure, and I can put

(eval-after-load "bytecomp"
  '(fset 'byte-compile-file
         (lambda (&rest ignore) (error "lirum larum"))))

into my .emacs and bytecompiling will also yield different results
depending on local setting. I guess that would also be relevant here.
         
    Oliver
-- 
16 Floréal an 214 de la Révolution
Liberté, Egalité, Fraternité!