Re: Problem with parenthesis matching and autoindentation in MacOS X version of emacs

[Alan Mackenzie <acm@muc.de>]

Hi, Juha!

On Mon, Dec 15, 2008 at 01:18:42PM +0200, Juha Nieminen wrote:
>   I'm using emacs in MacOS X, and it reports its version as:
> GNU Emacs 22.1.50.1 (i386-apple-darwin8.10.1, Carbon Version 1.6.0) of 
> 2007-08-20 on macpro

>   It has an annoying problem/bug regarding parenthesis matching and 
> autoindentation. (These problems do not happen in the linux nor the 
> Windows versions.) For example if I write this code in C++ mode:

> void foo()
> {
>     if(x < 0 || x >= puzzleWidth || y < 0 || y >= puzzleHeight)
>         {
>         }
> }

> it will report a "Mismatched parenteses" at the parenthesis which ends 
> the if conditional, and after that it will autoindent the {} symbols 
> wrongly (as seen above). If I replace the above with this:

> void foo()
> {
>     const bool isOutside =
>         x < 0 || x >= puzzleWidth || y < 0 || y >= puzzleHeight;
>     if(isOutside)
>     {
>     }
> }

> then it will not report the mismatch, and will indent the {} properly.

>   Any idea what could be wrong?

Yes.  There're bugs in C++ Mode to do with template brackets (who on
earth "designed" this feature in C++?).  C++ Mode is probably marking
your (newly typed) "<" and ">" as template delimiters, than unmarking the
">" as soon as it has become a ">=".

In C++, it's impossible, in the general case, to distinguish < "less
than" from < "open template", unless the thing doing the analysis is a
compiler.  C++ Mode tries to mark template delimiters as parentheses, but
sometimes it gets it badly wrong.  I've almost finished a fix for a
problem here, which I'm hoping will be ready in time for Emacs 23.  (Hi,
Yidong and Stefan!).

Please try your code snippets in C mode.  There probably isn't a problem
there.  If there is, could you report it to bug-cc-mode@gnu.org, please.

> (As said, this doesn't happen in linux nor Windows.)

I suspect this isn't actually the case.  Whether or not problems appear
is highly dependent on the order you type the characters.  Anyhow, I'm
trying to fix the cause of the problem by always marking "<" and ">" as
parens in matching pairs.

Could you please check again, typing the EXACT SAME sequence of
characters on the Mac and either GNU/Linux or Windows, whether you
actually do get different results on different systems.  Thanks in
advance!

-- 
Alan Mackenzie (Nuremberg, Germany).