Re: Feature freeze on October 1

[Stefan Monnier]

> In ccl.c, ccl_driver uses DECODE_CHAR, and ccl_driver itself
> has no problem because it doesn't uses a pointer into
> buffer/string.  But, I noticed that the callers of that
> function in coding.c (decode_coding_ccl and
> encode_coding_ccl) has to prepare for buffer relocation.
> I've just installed a fix.

Great, thank you.

>> (CODING_DECODE_CHAR seems to try and handle it explicitly, but I'm not
>> sure it's sufficient).
> At least, it should be sufficient for pointers used by code
> conversion routines.  Isn't it?

I have no particular reason to think it's not sufficient, but I haven't
looked closely enough to convince myself that it is.


        Stefan