From: Ingo Lohmar <i.lohmar@gmail.com>
To: jostein@kjonigsen.net, 23053@debbugs.gnu.org
Subject: bug#23053: 25.0.92; error in cc-mode when editing C# file with a generic class inheritance
Date: Sat, 19 Mar 2016 00:08:04 +0100 [thread overview]
Message-ID: <87wpozbd0r.fsf@acer.localhost.com> (raw)
In-Reply-To: <1458336813.1207699.553441090.44208CA4@webmail.messagingengine.com>
On Fri, Mar 18 2016 22:33 (+0100), Jostein Kjønigsen wrote:
> While the error is encountered in csharp-mode (which is a non-official
> Emacs-package) I think it's worth nothing that this didn't use to cause
> errors in the past.
>
> I've run this test-case against the "regular" Windows build 24.5.1,
> using latest csharp-mode package and it runs fine. Trying latest Emacs
> from git master on Ubuntu I can reproduce this error systematically
> using the exact same version of csharp-mode.
>
> In my opinion that makes this an Emacs-bug.
>
> Whatever changes was done with cc-mode, it seems they're not fully
> compatible with all derived modes out there. It might be worth reaching
> out to other known third-party mode-developers basing their work on
> cc-mode to see if they too have issues with the recent changes in git
> master?
It is quite daring to call out an Emacs bug when you only encounter a
problem in "random" 3rd-party code :)
I have used csharp-mode before --- unless something has dramatically
changed in the last 3 months, it is essentially unmaintained.
Also, and I hope this does not sound too harsh, the csharp-mode code has
its fair share of problems to begin with. For example, it uses faces
and cc-mode variables in ways that they are not intended for.
Therefore, it is plagued by more or less subtle font-lock and
indentation bugs. It has severe performance problems. It has not been
updated to deal w/ recent C# additions. It is also fairly bloated,
adding "features" only remotely related to editing C# code.
About a year ago, I started to strip down the code to the bare
essentials and tried to make it more robust and play nicely with the
cc-mode machinery. While this worked.. hmmm.. ok for the most part, I
have hesitated to put any of that code out in the open, as some of the
above problems remain unsolved. My take-away was that cc-mode is a big
and complex beast as it stands, and I am not too eager to dive into all
its details. If nobody else is doing the dirty work, chances to
properly support C# in *this* framework are pretty slim, I guess.
My hope is that the open-sourced Roslyn framework that is now used in
Omnisharp (haven't tested it) could also be used to do the whole
font-lock/indentation thing, such that we would not have to try to fit
C# into the cc-mode shape.
next prev parent reply other threads:[~2016-03-18 23:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 9:07 bug#23053: 25.0.92; error in cc-mode when editing C# file with a generic class inheritance Saulius Menkevičius
2016-03-18 21:13 ` bug#23053: followup on 23053 Saulius Menkevičius
2016-03-18 21:33 ` bug#23053: 25.0.92; error in cc-mode when editing C# file with a generic class inheritance Jostein Kjønigsen
2016-03-18 23:08 ` Ingo Lohmar [this message]
2016-03-19 7:29 ` Jostein Kjønigsen
2016-03-19 8:27 ` Jostein Kjønigsen
2016-03-21 12:26 ` Alan Mackenzie
2016-03-21 12:45 ` Jostein Kjønigsen
2016-03-21 21:53 ` Saulius Menkevičius
2016-03-22 10:21 ` Jostein Kjønigsen
2016-03-25 18:54 ` Alan Mackenzie
2016-03-26 7:26 ` Jostein Kjønigsen
2016-03-26 10:48 ` Alan Mackenzie
2016-03-19 10:05 ` Ingo Lohmar
2016-03-19 15:00 ` jostein
2016-03-19 17:54 ` Jostein Kjønigsen
2016-03-20 20:57 ` Jostein Kjønigsen
[not found] ` <mailman.7741.1458315553.843.bug-gnu-emacs@gnu.org>
2016-03-19 13:14 ` Alan Mackenzie
2016-03-19 14:15 ` Saulius Menkevičius
2016-03-20 21:16 ` Alan Mackenzie
2016-03-21 21:51 ` Saulius Menkevičius
2016-03-26 10:55 ` Alan Mackenzie
2016-03-26 10:59 ` Alan Mackenzie
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=87wpozbd0r.fsf@acer.localhost.com \
--to=i.lohmar@gmail.com \
--cc=23053@debbugs.gnu.org \
--cc=jostein@kjonigsen.net \
/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.