Re: [PATCH] Unicode Lisp reader escapes

[Aidan Kehoe]

 Ar an dara lá de mí Bealtaine, scríobh Kenichi Handa: 

 > > +  lisp_char = call2(intern("decode-char"), intern("ucs"),
 > > +                    make_number(i));
 > > +
 > 
 > First of all, is it safe to call Lisp program in read_escape? Don't we
 > have to care about GC and buffer/string-data relocation?

Yay, a technical objection. 

If it isn’t safe to call a Lisp program in read_escape, then the function is
full of bugs already. It’s called with three arguments, a Lisp_Object
readcharfun, an integer, and a pointer to an integer. If readcharfun is a
Lisp function (it may not be, it may be a buffer, a marker, or a string),
then that Lisp function is called on line 348. Cf. the documentation of
`read', which describes that the input may be from a function. 

-- 
Aidan Kehoe, http://www.parhasard.net/