Re: [PATCH] Flymake support for C/C++

[Reuben Thomas]

On 14 October 2017 at 17:29, João Távora <address@hidden> wrote:

Reuben Thomas <address@hidden> writes:

> On 14 October 2017 at 09:00, Eli Zaretskii <address@hidden> wrote:
> ​See
> ​http://www.flycheck.org/en/latest/user/flycheck-versus-flymake.html#flycheck-versus-flymake​

That page is now completely outdated. If you have a serious interest in
updating it, I can provide you with information about the new Flymake
that isn't already in its manual. Otherwise, please don't advertise a
misleading comparison.

The page invites corrections, so ​I suggest you edit it yourself and submit a pull request, or ​simply list some updates in an issue at 

https://github.com/flycheck/flycheck/issues

​It's certainly good to have it up to date; the page does contain a disclaimer about the versions of Flymake and Flycheck being compared, at least, so I don't think it's misleading.​

I believe it is generally naive to think such a thing.  But
specifically, I've had a look at flycheck.el and (again, if you are
really interested) I am willing to debate why I think parts of its
implementation are inferior to my rewrite of Flymake.

It sounds as though I've underestimated your improvements; I'm sorry. I agree that it's good to have a strong alternative.

Finally, being in Emacs also means it gets the care and attention of a
very talented group of programmers that share the common goal of
improving GNU and Emacs as a whole.

​It's not necessary for it to be in Emacs for that to happen (though I admit it will probably get more attention as a part of Emacs), and the more code that is in Emacs, the greater the maintenance burden for any change or new feature.

I would like to see more packages being spun out into independent projects, and packages that are currently imported into git from upstream (such as Org and CEDET) removed from git (though I appreciate that to have them available for all users it will be necessary to test them with releases, and it may be necessary to include them in source releases).

--

https://rrt.sc3d.org