For instance there is a feature called flymake-mode in Emacs lingo, to automatically compile check the code currently editet and to flag errors "on the fly".
...BUT with the difference that this is enabled per default in Komodo (maybe you already wondered how Komodo achieves to underline problematic code lines in red)
Unfortunately this opens a new security issue, not only installing a Perl module can be dangerous, already just opening in some editors can be harmful.
Just putting a BEGIN { ...do something evil ...} hidden somewhere in investigated code will cause surprising effects for unwary Komodo users opening it...
Maybe someone feels motivated now to mail some files to colleagues using Active State editors?
Or do you know fellow programmers automatically opening perl code web links in their editor of choice? ;-)
Cheers Rolf
PS: I remember slightly that one of the first big hacking attacks was carried out in the 80s by abusing an emacs vulnerability ...
The only approach I can think of to solve this issue (beside deactivating the feature by default) is to automatically replace each BEGIN, CHECK and UNITCHECK block with something like sub __BEGIN__ { ... } before running perl -c...
|
|---|