RFC: Structure of background parser and language support

Jens Herden jens at kdewebdev.org
Wed Jul 11 17:06:59 UTC 2007

> I don't think this is really what you want.  A language is much more
> than just a parser.  It is also the duchain and code completion
> specializations, supports code navigation, etc...  A language support
> supports more than one MIME type in the sense that a javascript language
> support could be loaded for:
> text/html files
> text/javascript files
> text/php files
> etc...  In the same sense a text/php file could load a php language
> support, html language support, javascript langauge support, etc...

Do you mean that for a text/html file we would load javascript, php, python, 
html, xml (could be xhtml) ... language support parts? I mean we actually 
don't know what is inside of the file and all different language support 
parts would have to parse it, right?
I don't think this would work very well. Actually Quanta might want to parse 
the same file with different parsers. First an HTML parser which detects 
embedded scripts and than with the suitable script parser. 

I think for web development the one parser fits all approach does not work.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20070711/b3248fa1/attachment.sig>

More information about the KDevelop-devel mailing list