[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: qt4.xml -> qt.xml
From:       Milian Wolff <mail () milianw ! de>
Date:       2014-02-24 8:52:54
Message-ID: 25801614.9RpVavX01m () minime
[Download RAW message or body]

On Monday 24 February 2014 08:34:54 Christoph Cullmann wrote:
> > I also agree with pretty much everything that was said in this thread: Up
> > to now, we never had any complaints about our cpp.xml highlighting too
> > many keywords,
> > 
> > I didn't complain... instead, I've started [my highlighter](
> > http://kde-files.org/content/show.php/?content=90660 ) because of "too
> > many
> > (mostly invalid) keywords"...
> > 
> > 
> > 
> > Alex (T.), would you agree to these changes (it might require more
> > changes)?
> > 
> > sure... if most of developers want this, I'm ok with that decision.
> > I'm going to stop contributing to this highlighter and will continue to
> > maintain my own at kde-files.org as it was before...
> > 
> > 
> > Just one cpp.xml (or, if you really want, one vanilla cpp.xml and on cpp-
> > qt.xml with higher priority).
> > 
> > I don't care anymore... (and of cause I wouldn't do this, so anyone who
> > care, please do whatever you want)
> 
> Couldn't we just to it the other way around?
> 
> We move the current cpp.xml to isocpp.xml.
> 
> And we agree that inside that, only stuff should be highlighted that is
> either in the current C++11 standard or in the draft of the next 1y
> standard.
> (and doxygen comments/alerts/...)

That's what we hvae with cpp.xml already. It could be kept that way.

> Then we move the qt4.xml to cpp.xml, it includes the isocpp.xml rules like
> it does atm the C++ rules and we add qt5 support to it.

We can leave the name at qt4.xml - just giving it a higher priority.

> That way at least we could share a common ISO C++ highlighting, which then
> can be used as base from others to include its rules to have e.g. boost
> c++/wxwidget c++/....

Thats already implemented like that with cpp.xml, no?

Bye
-- 
Milian Wolff
mail@milianw.de
http://milianw.de
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]