Re: Feature freeze on October 1

[Eli Zaretskii]

> From: Kenichi Handa <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden
> Date: Wed, 26 Sep 2012 22:57:35 +0900
> 
> In article <address@hidden>, Eli Zaretskii <address@hidden> writes:
> 
> > > #define CHAR_STRING_ADVANCE_NO_UNIFY CHAR_STRING_ADVANCE
> > > #define STRING_CHAR_ADVANCE_NO_UNIFY STRING_CHAR_ADVANCE
> > > 
> > > Then we won't forget that callers expect non-unify versions.
> 
> > Done as trunk revision 110196.
> 
> Thank you!

Thanks for your guidance.

> By the way, I vaguely remember that some workaround code was
> added to avoid the buffer relocation problem.  Do you
> remember where was it?  Or, is it just my false memory?

Your memory is fine.  The workaround code is in ralloc.c and in
maybe_unify_char.  But since we still call maybe_unify_char in
decode_char, I don't think we can remove those workarounds yet, can
we?