Ultraedit Syntax Highlighting and POD unmatched quotes

QM has asked for the wisdom of the Perl Monks concerning the following question:

Are there any tweaks to the language file that will let Ultraedit handle unmatched POD quotes correctly in syntax highlighting?

For instance:

=item blah

What's going on here?

=cut
[download]

Any code after =cut will appear to be part of a string (as will everything after the lone quote), until the next open quote. Large sections of code are thus not syntax highlighted.

-QM
--
Quantum Mechanics: The dreams stuff is made of

Comment on Ultraedit Syntax Highlighting and POD unmatched quotes Select or Download Code

Replies are listed 'Best First'.
Re: Ultraedit Syntax Highlighting and POD unmatched quotes by choroba (Cardinal) on Nov 20, 2012 at 15:48 UTC
I do not have Ultraedit to test against, but maybe a simple `=for Ultraedit '` [download] before the `=cut` can help? لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ	[reply] [d/l] [select]
Re^2: Ultraedit Syntax Highlighting and POD unmatched quotes by QM (Parson) on Nov 22, 2012 at 15:11 UTC
Having a deeper look at the code I'm hacking on, it didn't start the main POD block with `=pod`. My uew file only had this defined for block comments: `Block Comment On = =pod Block Comment Off = =cut` [download] Adding in `=item` to the uew file, and adding `=pod` to the perl file (it was missing) fixed a lot of problems. `Block Comment On Alt = =item Block Comment Off Alt = =cut` [download] Still, UE should allow multiple pairs of these (and a few other things). -QM -- Quantum Mechanics: The dreams stuff is made of	[reply] [d/l] [select]
Re: Ultraedit Syntax Highlighting and POD unmatched quotes by Anonymous Monk on Nov 20, 2012 at 22:18 UTC
Switch to SciTE/Padre/Kephra... very close to UltraEdit, better highlighting support	[reply]
Re: Ultraedit Syntax Highlighting and POD unmatched quotes by afoken (Chancellor) on Nov 21, 2012 at 18:56 UTC
Yes, UE's syntax highlighing has several problems. It was designed too simple, based simply on pattern matching and not on understanding the language, and so some extensions were added. They fixed some problems, but not all. Multi-line strings still confuse the highlighter, and embedded languages (Javascript and CSS in HTML, SQL and POD in Perl) are simply impossible. It's a mess, and no extension will be able to fix it. Live with it, add a `# '` here and a `# "` there, or use a different editor. I'm still searching for one. Some came close, but I've not yet found a single editor having all the features that I want to have. Emacs seems to have pretty good syntax highlighting, and it has tons of other features, but I simply don't like it. Too many features, too much wannabe operating system, too much desktop environment, and somewhere burried below all features lives a tiny editor. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l] [select]