From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r109223: Utility function to make a list from specified amount of objects.
Date: Fri, 27 Jul 2012 13:37:25 +0300 [thread overview]
Message-ID: <836299jxqy.fsf@gnu.org> (raw)
In-Reply-To: <501249A3.1090103@yandex.ru>
> Date: Fri, 27 Jul 2012 11:56:19 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> Cc: emacs-diffs@gnu.org, Emacs development discussions <emacs-devel@gnu.org>
>
> On 07/27/2012 10:45 AM, martin rudalics wrote:
>
> > revno: 109223
> > committer: Dmitry Antipov <address@hidden>
> > branch nick: trunk
> > timestamp: Fri 2012-07-27 10:04:35 +0400
> > message:
> > Utility function to make a list from specified amount of objects.
> > * lisp.h (enum constype): New datatype.
> > (listn): New prototype.
> > * alloc.c (listn): New function.
> > (Fmemory_use_count, syms_of_alloc): Use it.
> > * buffer.c (syms_of_buffer): Likewise.
> > * callint.c (syms_of_callint): Likewise.
> > * charset.c (define_charset_internal): Likewise.
> > * coding.c (syms_of_coding): Likewise.
> > * keymap.c (syms_of_keymap): Likewise.
> > * search.c (syms_of_search): Likewise.
> > * syntax.c (syms_of_syntax): Likewise.
> > * w32.c (init_environment): Likewise.
> > * w32fns.c (Fw32_battery_status, syms_of_w32fns): Likewise.
> > * xdisp.c (syms_of_xdisp): Likewise.
> > * xfns.c (syms_of_xfns): Likewise.
> >
> > gets me
> >
> > w32.c: In function 'init_environment':
> > w32.c:1727:34: error: expected ')' before ';' token
> > make[1]: *** [oo/i386/w32.o] Error 1
> > make[1]: Leaving directory `c:/emacs/trunk/src'
> > make: *** [all-other-dirs-gmake] Error 2
In addition, there was a more serious error in listn: it consed the
arguments in the wrong order: from first to last, instead of the other
way around. This caused incorrect frame title to be displayed, but
also had other manifestations: e.g., memory-use-counts would display
its results in the reversed order.
(I fixed listn in revision 109230.)
Dmitry, I wonder how you tested listn, that left these problems
undetected. Just stepping into memory-use-counts with a debugger and
comparing the values of the variables with the list returned to Lisp
should have shown the problem very clearly.
next prev parent reply other threads:[~2012-07-27 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50123904.9040005@gmx.at>
2012-07-27 7:56 ` [Emacs-diffs] /srv/bzr/emacs/trunk r109223: Utility function to make a list from specified amount of objects Dmitry Antipov
2012-07-27 8:21 ` martin rudalics
2012-07-27 9:12 ` Andy Moreton
2012-07-27 9:15 ` Eli Zaretskii
2012-07-27 9:25 ` Eli Zaretskii
2012-07-27 9:31 ` martin rudalics
2012-07-27 9:17 ` [Emacs-diffs] " Dmitry Antipov
2012-07-27 9:28 ` Eli Zaretskii
2012-07-27 10:37 ` Eli Zaretskii [this message]
2012-07-27 10:59 ` Dmitry Antipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=836299jxqy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).