Re: composition bug

[Kenichi Handa <handa@m17n.org>]

In article <jwv3ajy7zvr.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

> > I'm always confused by int and EMACS_INT.  "struct it" and
> > "struct text_pos" in dispextern.h uses "int" for
> > buffer/string positions, and xdisp.c calls functions in
> > composite.c with those values.  So, there exist mixture of
> > int and EMACS_INT.  Shouldn't all of them use EMACS_INT for
> > positions (and perhaps for string length)?

> Yes.  It's important for buffers (or strings) larger than 2GB.
> We probably don't need to worry about strings larger than 2GB for a few
> more years, but for buffers it's worthwhile to take it into account.

As I don't have a time to work on it at the moment, I added
this section in admin/FOR-RELEASE.

** In C, use EMACS_INT for variables and structure members
for buffer/string positions.  E.g. struct it, struct text_pos.

---
Kenichi Handa
handa@ni.aist.go.jp