Questions with Vim’s Creator, Bram Moolenaar

Re:Questions with Vim’s Creator, Bram Moolenaar by ggreer on Wednesday November 19, 2014 @10:32PM (#8634295)

Are you familiar with Vim's code? Just look at all the OS-specific files in the source tree[1]. Not only that, there are ifdefs-galore in the shared code. RealWaitForChar is over 400 lines and contains 41 ifdefs.[2] Many are for long-dead features or platforms. That function just waits for user input, but it has to be ridiculously complicated to account for platforms without basic functions like select(). The infamous eval.c starts off with ifdefs for Amiga, VMS, and Mac OS Classic.[3] Neovim has ripped out tons of this stuff, and it's drastically reduced line count.

1. https://github.com/b4winckler/macvim/tree/master/src

2. https://github.com/b4winckler/macvim/blob/master/src/os_unix...

3. https://github.com/b4winckler/macvim/blob/master/src/eval.c

[ Parent | on HN ]

Re:Questions with Vim’s Creator, Bram Moolenaar by dllthomas on Thursday November 20, 2014 @04:31PM (#8638280)

I think the parent can be read as an honest request for more details. It doesn't need to be met with snark.

(Don't take this too harshly - the content in your post is good.)

[ Parent | on HN ]

Re:Questions with Vim’s Creator, Bram Moolenaar by SamReidHughes on Friday November 21, 2014 @01:10PM (#8642457)

How does this stuff get in the way of the features that NeoVim intends to add? -- features they list such as "job control", a msgpack remote API, or a new plugin architecture. (I don't really expect you to be capable of answering this question unless you're familiar enough with the code to give an operational description of how these ifdefs get in the way.)

[ Parent | on HN ]