unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: luangruo@yahoo.com, jonas@bernoul.li, emacs-devel@gnu.org
Subject: Re: Transient manual
Date: Fri, 01 Sep 2023 09:41:23 +0300	[thread overview]
Message-ID: <837cpacs4s.fsf@gnu.org> (raw)
In-Reply-To: <E1qbsl6-0006m6-7a@fencepost.gnu.org> (message from Richard Stallman on Thu, 31 Aug 2023 21:15:36 -0400)

> From: Richard Stallman <rms@gnu.org>
> Cc: jonas@bernoul.li, emacs-devel@gnu.org
> Date: Thu, 31 Aug 2023 21:15:36 -0400
> 
>   > Texinfo 4.13 is also the final version of Texinfo written in C; it is
>   > several orders of magnitude faster than anything newer.
> 
> Could you give us an real example of the time difference between the
> versions, on a real input job?  That would help us understand the
> impact of this issue.

Current version of makeinfo is about 10 times slower than the one from
Texinfo 4.13 if Perl extensions (written in C as part of Texinfo) are
used, and about 15 to 18 times slower if the extensions are not used
(i.e. only Perl code is used for all the Texinfo-to-Info translation).

Of course, current Texinfo has many features that 4.13 didn't support
and many of them simply could not be supported without a complete
redesign and reimplementation of makeinfo as it was originally
designed.  Its one-pass architecture with conversions performed
in-place on the same input buffer simply made some complex features
impossible to implement.  That design is what made it so
lightning-fast, but also put a limit to its extensibility and
development.



  reply	other threads:[~2023-09-01  6:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87cyz6wtja.fsf.ref@yahoo.com>
2023-08-29  1:01 ` Transient manual Po Lu
2023-08-30  0:10   ` Jonas Bernoulli
2023-08-30  1:08     ` Po Lu
2023-08-30  2:25       ` Eli Zaretskii
2023-09-01  1:15       ` Richard Stallman
2023-09-01  6:41         ` Eli Zaretskii [this message]
2023-08-30  5:16     ` Ihor Radchenko
2023-09-01 23:22       ` Jonas Bernoulli
2023-09-02  7:14         ` Ihor Radchenko
2023-09-02 16:31           ` Jonas Bernoulli
2023-09-02 17:12             ` Ihor Radchenko
2023-08-30  2:05   ` Richard Stallman

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=837cpacs4s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jonas@bernoul.li \
    --cc=luangruo@yahoo.com \
    --cc=rms@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).