This is a comment following on from the file format <=> session complaints from Marjolein Katsma posted with the important notice from Tim:-
http://www.scootersoftware.com/cirru...splay.php?f=12
Where mixed language formats are embedded within each other, such as HTML in PHP files and HTML in ASP files, then the language interpretation / highlighting falls down. One solution was to switch fiel formats depending on what you are looking at in the file.
I use the gvim editor a lot http://www.vim.org/index.php
That has a very simple, but extremely powerful concept in its language files - it knows from the language syntax what language you are now 'changing' to, and will therefore switch its highlighting to that new language. Likewise the new language has constructs that know when it is terminating back to another language.
Thus, when I look at a PHP file, the HTML parts are highlighted as per the HTML syntax, and the PHP parts as per the PHP syntax. SQL statements are highlighted using SQL syntax rules.
Perhaps a future release could extend the file formats so that it knows the syntax for embedding other languages, and will switch to that other file format (on a stack basis), switching back when the other format reaches an 'end' syntax.
Use of such an automatic feature will make PHP, ASP, etc far easier to compare.
http://www.scootersoftware.com/cirru...splay.php?f=12
Where mixed language formats are embedded within each other, such as HTML in PHP files and HTML in ASP files, then the language interpretation / highlighting falls down. One solution was to switch fiel formats depending on what you are looking at in the file.
I use the gvim editor a lot http://www.vim.org/index.php
That has a very simple, but extremely powerful concept in its language files - it knows from the language syntax what language you are now 'changing' to, and will therefore switch its highlighting to that new language. Likewise the new language has constructs that know when it is terminating back to another language.
Thus, when I look at a PHP file, the HTML parts are highlighted as per the HTML syntax, and the PHP parts as per the PHP syntax. SQL statements are highlighted using SQL syntax rules.
Perhaps a future release could extend the file formats so that it knows the syntax for embedding other languages, and will switch to that other file format (on a stack basis), switching back when the other format reaches an 'end' syntax.
Use of such an automatic feature will make PHP, ASP, etc far easier to compare.
Comment