I'm not seeing this behavior, as I've been doing test-driven Perl development in Eclipse/EPIC for quite a while, and it would have been a showstopper.
Currently, I'm running EPIC 0.6.35 on Eclipse 3.5, but I've been using various versions since Eclipse 3.2.
Are *.t files associated with "Epic Perl Editor" in Preferences->General->Editors->File Associations ?
As a test, try right-clicking and selecting "Open With" and forcing "Epic Perl Editor".
Standard advice is to make sure you're running the "testing" version and using Sun's JVM if you're on Linux, which you well might be if you're the Andreas Pohl I remember, but I don't know of .t files not being syntax validated as long as they're being opened in the Epic editor.
In fact, that method even works to open *nix-style files with no extension, and the Perl property is sticky.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not seeing this behavior, as I've been doing test-driven Perl development in Eclipse/EPIC for quite a while, and it would have been a showstopper.
Currently, I'm running EPIC 0.6.35 on Eclipse 3.5, but I've been using various versions since Eclipse 3.2.
Are *.t files associated with "Epic Perl Editor" in Preferences->General->Editors->File Associations ?
As a test, try right-clicking and selecting "Open With" and forcing "Epic Perl Editor".
Standard advice is to make sure you're running the "testing" version and using Sun's JVM if you're on Linux, which you well might be if you're the Andreas Pohl I remember, but I don't know of .t files not being syntax validated as long as they're being opened in the Epic editor.
In fact, that method even works to open *nix-style files with no extension, and the Perl property is sticky.
Closed: Validation of .t files works for sure.