[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Alan Mackenzie
Subject: Re: [PATCH] Flymake support for C/C++
Date: Sun, 3 Jun 2018 13:44:00 +0000
User-agent: Mutt/1.9.4 (2018-02-28)

Hello, Stefan.

On Sat, Jun 02, 2018 at 11:26:54 -0400, Stefan Monnier wrote:
> > I must admit not to being too keen on CC Mode changing like this; it
> > would spoil the unity of purpose of the mode.  I've glanced through the

> What is "the unity of purpose of" CC-mode?

That feels like a rhetorical question.  It's dealt with in standard
software engineering texts.

I think it's also clear.  If it's not, to anybody, it's probably not that

> >>From where I stand, your position on this patch amounts to saying "I
> don't want to make it easier for users of CC-mode to use flymake-mode".

That's indeed the case, with empasis on the "I".  I've got enough other
things to do that I don't want to spend time contributing to
flymake-mode.  But I've got nothing against João or anybody else, doing

However, I'm concerned to get the optimum interface between CC Mode and
flymake-mode, and right at the moment that would appear to be none

> Yet AFAIK the purpose of CC-mode is to help users of C-like languages
> make the best use of Emacs.

CC Mode in concert with all the other facilities of Emacs.  CC Mode
doesn't include Cedet, trailing-space facilities, movement between
matching parentheses, font-locking infrastructure, redisplay
infrastructure, or any of the many other Emacs features useful with or
necessary to C(etc.) Mode.  Nor should it.  One of these other features
is flymake mode.  It shouldn't be included in CC Mode either.

> I'm having trouble reconciling those different statements into
> a coherent whole.

>         Stefan

Alan Mackenzie (Nuremberg, Germany).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]