From: David Engster <deng@randomsample.de>
To: Anand Tamariya <atamariya@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Semantic font-lock for Java
Date: Tue, 28 Jan 2020 18:21:09 +0100 [thread overview]
Message-ID: <878slr5wfu.fsf@randomsample> (raw)
In-Reply-To: <CADm7Y4mqXxQBbFd=c+gGDpsrjQGgsmrHuhgq6Yc5vjNz2+epPw@mail.gmail.com> (Anand Tamariya's message of "Tue, 28 Jan 2020 21:20:53 +0530")
> So my guess is the scroll benchmark is simply 17% slower
>
> because there are more overlays in the buffer, not because of
> actual
> parsing.
>
> Perfect explanation David. Though I'll add that parsing is not
> terribly slow. It's usable. Here's a demo video showcasing the same
> https://youtu.be/4UcPIdTJLOM .
Note that Semantic will cache the AST between sessions, so if you've
loaded that file before, it will just load the cache.
The time needed for parsing varies wildly between languages. The Java
parser is one of the faster ones, because it's an LALR parser, which is
more efficient than LL (which Semantic uses for C and C++). It is also
very old, and at that time (around Java 1.4 or so) the language was
still very easy to parse (it doesn't support generics, for instance).
-David
next prev parent reply other threads:[~2020-01-28 17:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 11:39 Semantic font-lock for Java Anand Tamariya
2020-01-21 15:41 ` Eli Zaretskii
2020-01-21 15:48 ` Eli Zaretskii
2020-01-22 5:13 ` Anand Tamariya
2020-01-22 17:25 ` Eli Zaretskii
2020-01-23 5:36 ` Anand Tamariya
2020-01-24 7:40 ` Eli Zaretskii
2020-01-24 16:15 ` Anand Tamariya
2020-01-24 16:20 ` Eli Zaretskii
2020-01-24 17:00 ` David Engster
2020-01-24 19:59 ` Eli Zaretskii
2020-01-24 20:38 ` David Engster
2020-01-28 15:50 ` Anand Tamariya
2020-01-28 17:21 ` David Engster [this message]
2020-01-28 17:50 ` Eli Zaretskii
2020-01-29 5:14 ` Anand Tamariya
2020-02-03 3:24 ` Eric Ludlam
2020-01-28 19:43 ` Alan Mackenzie
2020-01-29 5:44 ` Anand Tamariya
2020-01-22 5:52 ` Anand Tamariya
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=878slr5wfu.fsf@randomsample \
--to=deng@randomsample.de \
--cc=atamariya@gmail.com \
--cc=eliz@gnu.org \
--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).