all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juha Nieminen <nospam@thanks.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: Problem with parenthesis matching and autoindentation in MacOS X version of emacs
Date: Thu, 18 Dec 2008 00:32:25 GMT	[thread overview]
Message-ID: <tSg2l.274$Kp1.183@read4.inet.fi> (raw)
In-Reply-To: <mailman.2957.1229530429.26697.help-gnu-emacs@gnu.org>

Alan Mackenzie wrote:
>>   Would it be a great loss if the <> "brackets" were not included in the
>> matching logic at all?
> 
> It would be a loss, yes.  Maybe not that great, but it would be a loss in
> consistency, since paren matching should match any sort of
> parens/braces/brackets, etc.

  I know that the C++ language syntax is not a context-free grammar. In
other words, the meaning of tokens (eg. the tokens < and >) cannot be
deduced without the context.

  OTOH, it basically only makes the life of compilers and code editing
software harder, not people writing C++. It *is* the duty of programs to
do all the hard work, rather than leaving it to the user. :)

  OTOH, given that it's impossible to know the meaning of the < and >
symbols in C++ without the full context, I assume it will be impossible
to make any matching logic which would work in all cases. I don't really
think it would be a huge loss if those were not included in the
parenthesis matching rules.


      parent reply	other threads:[~2008-12-18  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 11:18 Problem with parenthesis matching and autoindentation in MacOS X version of emacs Juha Nieminen
2008-12-15 18:39 ` Alan Mackenzie
     [not found] ` <mailman.2805.1229365442.26697.help-gnu-emacs@gnu.org>
2008-12-16 19:46   ` Juha Nieminen
2008-12-17 16:29     ` Alan Mackenzie
     [not found]     ` <mailman.2957.1229530429.26697.help-gnu-emacs@gnu.org>
2008-12-18  0:32       ` Juha Nieminen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='tSg2l.274$Kp1.183@read4.inet.fi' \
    --to=nospam@thanks.invalid \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.