summaryrefslogtreecommitdiff
path: root/src/minibuf.c
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2014-07-26 06:17:25 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2014-07-26 06:17:25 -0700
commit9e9f8582a893f1e97b1f8955f69b96f969ee1f85 (patch)
treeef8b4c36f8b88d1273572b8140a8651854b65e6b /src/minibuf.c
parent54e3f15626296c1ece932852df2b3d4938b0b44a (diff)
downloademacs-9e9f8582a893f1e97b1f8955f69b96f969ee1f85.tar.gz
Revert previous change.
There is certainly nothing wrong with writing code like 'lo <= i && i <= hi', even if LO happens to a constant. There isn't even anything wrong in general with writing 'a <= b' if A happens to be a constant. At any rate stylistic changes shouldn't be done like this without discussion.
Diffstat (limited to 'src/minibuf.c')
-rw-r--r--src/minibuf.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/minibuf.c b/src/minibuf.c
index e4f81906873..b85d3f57df3 100644
--- a/src/minibuf.c
+++ b/src/minibuf.c
@@ -265,7 +265,7 @@ read_minibuf_noninteractive (Lisp_Object map, Lisp_Object initial,
fprintf (stdout, "%c", hide_char);
if (len == size)
{
- if (size > STRING_BYTES_BOUND / 2)
+ if (STRING_BYTES_BOUND / 2 < size)
memory_full (SIZE_MAX);
size *= 2;
line = xrealloc (line, size);