[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: composition bug
From: |
Stefan Monnier |
Subject: |
Re: composition bug |
Date: |
Thu, 18 Sep 2008 02:08:02 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
> 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.
Stefan
- Re: composition bug, (continued)
- Re: composition bug, Kenichi Handa, 2008/09/10
- Re: composition bug, Romain Francoise, 2008/09/11
- Re: composition bug, Romain Francoise, 2008/09/13
- Re: composition bug, Kenichi Handa, 2008/09/16
- Re: composition bug, Romain Francoise, 2008/09/16
- Re: composition bug, Kenichi Handa, 2008/09/16
- Re: composition bug, Romain Francoise, 2008/09/16
- Re: composition bug, Kenichi Handa, 2008/09/17
- Re: composition bug, Romain Francoise, 2008/09/17
- Re: composition bug, Kenichi Handa, 2008/09/17
- Re: composition bug,
Stefan Monnier <=
- Re: composition bug, Kenichi Handa, 2008/09/18
- Re: composition bug, Stefan Monnier, 2008/09/18
- Re: composition bug, Kenichi Handa, 2008/09/18