I've spent the last 2 hours trying to find a way to benchmark syntax.
The easiest way I found to reproduce the speed regression is [1]
included patches: 1148
results:
engine 0 0.568 total
engine 1 0.194 total (1/3 of time)
engine 2 0.564 total
$COLUMS = 146
$LINES = 40
(s
2013年6月9日日曜日 6時48分39秒 UTC+9 Bram Moolenaar:
> Shougo wrote:
>
>
>
> > > The solution I've been thinking of is www.zimbu.org.
>
> > > It produces C code, thus there should be a way to mix some parts written
>
> > > in Zimbu and some parts still written in C.
>
> >
>
> > I think Zimbu is not
Excerpts from Bram Moolenaar's message of Sat Jun 08 23:48:39 +0200 2013:
> There are no options. Vim is written in C and I see no reason to
> change.
Your reply is not complete yet. My question was:
How to use collections without repeating myself while coding.
Vim is about "not repating yourself
> Yeah, basic C is missing containers. There are libraries for them, but
> there doesn't seem to be one clear winner.
How about define common containers for Vim by C?
And rewriting Vim by using that containers gradually.
Absence of common containers in Vim, have caused duplication of
implement
Marc Weber wrote:
> Excerpts from Shougo's message of Sat Jun 08 19:09:04 +0200 2013:
> > How is the Go language?
> > I think Go is similar to Zimbu.
> > What are Zimbu advantages compared from Go language?
> Same problem about Go/whatever? How to upgrade without rewriting
> everything?
>
> I'm
Shougo wrote:
> > The solution I've been thinking of is www.zimbu.org.
> > It produces C code, thus there should be a way to mix some parts written
> > in Zimbu and some parts still written in C.
>
> I think Zimbu is not bad choice.
> Zimbu is developped continuously by Mr.Bram and it fits with
Patch 7.3.1152
Problem:In tiny build ireg_icombine is undefined. (Tony Mechelynck)
Solution: Add #ifdef.
Files: src/regexp_nfa.c
*** ../vim-7.3.1151/src/regexp_nfa.c2013-06-08 23:26:10.0 +0200
--- src/regexp_nfa.c2013-06-08 23:29:22.0 +0200
***
***
Patch 7.3.1151
Problem:New regexp engine: Slow when a look-behind match is followed by a
zero-width match.
Solution: Postpone the look-behind match more often.
Files: src/regexp_nfa.c
*** ../vim-7.3.1150/src/regexp_nfa.c2013-06-08 22:29:59.0 +0200
--- src/regex
Excerpts from Shougo's message of Sat Jun 08 19:09:04 +0200 2013:
> How is the Go language?
> I think Go is similar to Zimbu.
> What are Zimbu advantages compared from Go language?
Same problem about Go/whatever? How to upgrade without rewriting
everything?
I'm not asking for a full rewrite, just
Patch 7.3.1150
Problem:New regexpengine: Slow when a look-behind match does not have a
width specified.
Solution: Try to compute the maximum width.
Files: src/regexp_nfa.c
*** ../vim-7.3.1149/src/regexp_nfa.c2013-06-08 18:19:39.0 +0200
--- src/regexp_nfa.c2
Tony Mechelynck wrote:
> After downloading 7.3.1146 to 7.3.1149, Huge build compiles but Tiny
> doesn't:
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
> -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> -o objects/regexp.o regexp.c
> In file included from
Excerpts from Bram Moolenaar's message of Sat Jun 08 12:56:38 +0200 2013:
> C++ is incredibly complex.
I didn't ask about introducing all kinds of odities. I know that doing
C++ proberly takes 2 years or more studying C++.
Now you can shoot yourself into your feet using any language.
I just want "
After downloading 7.3.1146 to 7.3.1149, Huge build compiles but Tiny
doesn't:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
-fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-o objects/regexp.o regexp.c
In file included from regexp.c:7903:0:
regexp_nfa.c: In fu
2013年6月9日日曜日 2時09分04秒 UTC+9 Shougo:
> 2013年6月8日土曜日 19時56分38秒 UTC+9 Bram Moolenaar:
>
> > Marc Weber wrote:
>
> >
>
> >
>
> >
>
> > > Well - I don't want to discuss the topic.
>
> >
>
> > >
>
> >
>
> > > I just want to know how to do basic stuff "the Vim way" efficiently.
>
> >
>
>
2013年6月8日土曜日 19時56分38秒 UTC+9 Bram Moolenaar:
> Marc Weber wrote:
>
>
>
> > Well - I don't want to discuss the topic.
>
> >
>
> > I just want to know how to do basic stuff "the Vim way" efficiently.
>
> >
>
> > C++ is not perfect, and probably its easiy to get things wrong.
>
> > But at le
Patch 7.3.1149
Problem:New regexp engine: Matching plain text could be faster.
Solution: Detect a plain text match and handle it specifically. Add
vim_regfree().
Files: src/regexp.c, src/regexp.h, src/regexp_nfa.c,
src/proto/regexp.pro, src/buffer.c, src/edit.c,
Addendum: If I use merely '/'s in the file name the error does not occur;
however, if I press once, all '/'s get converted into '\'s, leaving me at
the problem described above.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
When I try to expand into a directory whose name starts with '{', like in
w d:\temp\{
I receive error message E220. Although the error is described in the docs, it's
quite nasty on Windows where having a directory name like the one described
above isn't very common but also not uncommon for som
Patch 7.3.1148
Problem:No command line completion for ":syntime".
Solution: Implement the completion. (Dominique Pelle)
Files: runtime/doc/map.txt, src/ex_cmds.h, src/ex_docmd.c,
src/ex_getln.c, src/proto/syntax.pro, src/syntax.c, src/vim.h
*** ../vim-7.3.1147/runtime/doc/
On Sat, Jun 08, 2013 at 05:52:28AM +0200, Marc Weber wrote:
> It might make sense to introduce little benchmarking for regular
> expressions. Eg open such a file, then list which regex took how much
> cpu cycles or time.
Like the :syntime command that was added in patch 1129?
Cheers,
--
James
GP
Patch 7.3.1147
Problem:New regexp engine: regstart is only used to find the first match.
Solution: Use regstart whenever adding the start state.
Files: src/regexp_nfa.c
*** ../vim-7.3.1146/src/regexp_nfa.c2013-06-08 13:33:32.0 +0200
--- src/regexp_nfa.c2013-06-08 14:37
I wrote:
> Marc Weber wrote:
>
> > Try this file:
> > https://raw.github.com/jeremywohl/iphone-scripts/master/appstore_reviews
> >
> > copy paste it into a .rb file. This feel very slow to me.
> > I can watch Vim drawing blocks of lines. Using regexpengine=1 everything
> > is as fast as ever.
On 8 June 2013, Bram Moolenaar wrote:
>
> Marc Weber wrote:
>
> > Try this file:
> > https://raw.github.com/jeremywohl/iphone-scripts/master/appstore_reviews
> >
> > copy paste it into a .rb file. This feel very slow to me. I can
> > watch Vim drawing blocks of lines. Using regexpengine=1 ever
Patch 7.3.1146
Problem:New regexp engine: look-behind match not checked when followed by
zero-width match.
Solution: Do the look-behind match before adding the zero-width state.
Files: src/regexp_nfa.c
*** ../vim-7.3.1145/src/regexp_nfa.c2013-06-07 22:39:35.0 +
Marc Weber wrote:
> Well - I don't want to discuss the topic.
>
> I just want to know how to do basic stuff "the Vim way" efficiently.
>
> C++ is not perfect, and probably its easiy to get things wrong.
> But at least it provides standard ways for standard tasks, such as
> arrays/vectors/maps/h
Marc Weber wrote:
> Try this file:
> https://raw.github.com/jeremywohl/iphone-scripts/master/appstore_reviews
>
> copy paste it into a .rb file. This feel very slow to me.
> I can watch Vim drawing blocks of lines. Using regexpengine=1 everything
> is as fast as ever.
>
> patches: 1-1115
>
>
Dominique Pelle wrote:
> Attached patch adds command line completion to the
> recently added command :s:syntime commandyntime
Thanks! I predicted someone would come up with this, so I didn't spend
time on it :-).
--
hundred-and-one symptoms of being an internet addict:
108. While reading a ma
Dominique Pellé wrote:
> Hi
>
> Attached patch adds command line completion to the
> recently added command :s:syntime commandyntime
>
> Regards
> Dominique
Attached is a small update to the patch. The |...| were
missing around :syntime in runtime/doc/map.txt.
Dominique
--
--
You received thi
Hi
Attached patch adds command line completion to the
recently added command :s:syntime commandyntime
Regards
Dominique
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.o
On 08/06/2013 02:49, Marc Weber wrote:
Well - I don't want to discuss the topic.
I just want to know how to do basic stuff "the Vim way" efficiently.
C++ is not perfect, and probably its easiy to get things wrong.
But at least it provides standard ways for standard tasks, such as
arrays/vectors
On Jun 8, 2013 5:48 AM, "Marc Weber" wrote:
>
> Well - I don't want to discuss the topic.
>
> I just want to know how to do basic stuff "the Vim way" efficiently.
>
> C++ is not perfect, and probably its easiy to get things wrong.
> But at least it provides standard ways for standard tasks, such a
On Jun 7, 2013 9:17 PM, "Bram Moolenaar" wrote:
>
>
> Mike Williams wrote:
>
> > Following the other email on new regex performance here is a patch that
> > remove the memory available check on Win32 (i.e. XP, Vista, etc.) It's
> > accuracy was questionable on Win32 (numbers returned will most li
32 matches
Mail list logo
