Am Dienstag 26 September 2006 22:16 schrieb Sergei Steshenko:
--- Stephan Brunner <stephan brunner gmx de> wrote:
Am Montag 25 September 2006 08:55 schrieb Ratcliffe, Jeffrey (Peters):
Sorry for this being slightly off-topic, but:

Are any of you guys using an IDE?

For want of anything better, I am using nedit, which looks foul on
Ubuntu Dapper, but is a miles better editor than gedit.

On the editor-only-level, I use vim. You might want to try kate (if you
use KUbuntu...).

I tried out Eclipse + EPIC, but the editor was nowhere near as nice as
nedit and I could only get Perl syntax highlighting if the file was

I just installed Eclipse + EPIC myself these days (also Ubuntu Dapper).
So far, I like it somehow, mostly because of the Package Explorer and the
"Outline". It is definitly more efficient to select a specific subroutine
in the outline tree than browsing through bunches of files and pages of
code looking for it...
On the other hand, it is not the most responsive software I ever used:-)
And it's not as smart as I would like it to be.
Write, for example,

my $foo = Foo->new;
$foo-> (you get a selection of the available methods here, which is

But write (as it happens more often this way):

my $foo = shift;

The above is typically one of the first subroutine statements, meaning

my $foo = shift @_;
How can any IDE know how the subroutine will be called, i.e. what's
going to be on @_ array ?

Oops, of course you're right. My thoughts were inspired by C++, where the IDE 
knows how a function is called and which variable is of what type. Should 
have thought more about it. 
Still, code-completion isn't worth a lot under these conditions - but it isn't 
EPIC's fault:-)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]