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

List:       kwrite-devel
Subject:    Re: Default Styles
From:       Milian Wolff <mail () milianw ! de>
Date:       2014-02-17 22:49:13
Message-ID: 1605507.aGPzeSSX1Q () minime
[Download RAW message or body]

On Monday 17 February 2014 23:21:12 Philipp A. wrote:
> i'll comment a bit:

<snip>

> ? dsBuiltin: Value keywords like Java's true, R's FALSE, Python's None,
> 
> >              JS' null, as well as Python's open, reversed, ..., and Go's
> >              predeclared identifiers like new, print, ...
> > 
> > ? dsBuiltinValue
> > ? dsBuiltinFunction
> 
> i'm definitely for some combination of those, at least the one dsBuiltin.
> many languages have a list of those in their highlightning files and style
> them somehow.

Can you elaborate why you want to have that, and how it differs from 
dsKeyword, dsFunction, dsConstant?

Just the fact that other language highlight everything somehow differently, 
doesn't mean that it is a good idea. Imo, quite a few languages use to many 
styles.

> ? dsException: Often with Exception or Error in the name
> 
> i'm coming from python here. do other languages also have standard
> exception hierarchies? if not, scratch that.

At least JavaScript and C++ don't have it. PHP has it though. Anyhow, this 
depends on semantic analysis (see my other email) and maybe needs a different 
approach. That said, why would one want to highlight exceptions differently 
from other objects? Where is this useful to know directly whether a type is 
actually an Exception?

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]