[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8545: issues with recent doprnt-related changes
From: |
Eli Zaretskii |
Subject: |
bug#8545: issues with recent doprnt-related changes |
Date: |
Fri, 06 May 2011 18:03:46 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 8545@debbugs.gnu.org,
> emacs-devel@gnu.org
> Date: Fri, 06 May 2011 10:33:21 -0300
>
> And we never show "length, including
> terminating nul-byte" to Elisp, so the nul-byte shouldn't matter
If you are sure of that, then I agree it's fine to use
MOST_POSITIVE_FIXNUM+1. I wasn't sure. I do see in C variables that
explicitly use the string position of the null byte; I was afraid that
they could somehow leak to Lisp.
- bug#8545: issues with recent doprnt-related changes, (continued)
bug#8545: issues with recent doprnt-related changes, Paul Eggert, 2011/05/04
- bug#8545: issues with recent doprnt-related changes, Eli Zaretskii, 2011/05/04
- bug#8545: issues with recent doprnt-related changes, Paul Eggert, 2011/05/04
- bug#8545: issues with recent doprnt-related changes, Eli Zaretskii, 2011/05/05
- bug#8545: issues with recent doprnt-related changes, Stefan Monnier, 2011/05/06
- bug#8545: issues with recent doprnt-related changes, Paul Eggert, 2011/05/06
- bug#8545: issues with recent doprnt-related changes,
Eli Zaretskii <=
- bug#8545: issues with recent doprnt-related changes, Stefan Monnier, 2011/05/06
- bug#8545: issues with recent doprnt-related changes, Eli Zaretskii, 2011/05/06
- bug#8545: issues with recent doprnt-related changes, Stefan Monnier, 2011/05/06
- bug#8545: issues with recent doprnt-related changes, Eli Zaretskii, 2011/05/07