[Wellington-pm] IDEs round-the-room

Peter Kelly perlmonger at pck.co.nz
Sun Jun 25 14:05:36 PDT 2017

Thanks everyone for the round-the-room.  Traditionally I've used vim and
/say "variable is $variable" if $debug_level > x;/  But IDEs have some
merits - I do love being able to set a conditional breakpoint inside a
nested loop structure, and then hover over the name of the array-of-hashes
and click through it.  The perl command line debugger is pretty painful.
And I do introduce syntax errors as I work, no doubt more than the median

I did about 12 hours coding in Komodo over the weekend to try it out.
Komodo is very slow on the i5-powered computer I am using, although that
may be everything struggling with the 4K screen.  It is nice to be prompted
with function arguments, although they did tend to mysteriously disappear
once an argument was typed in.  But a two-second lag before it notices my
interim invalid-syntax code on the previous line is now OK is pretty

Perhaps I'll try Eclipse again ... it would feel a bit like moving back to
Lower Hutt ... I was glad to leave both behind :-/



On 25 June 2017 at 17:42, Florent Mara <florent.mara at nzregen.co.nz> wrote:

> I didn't mention usage for Smart::Comments instead of print / say debug
> statement.
> I have been using and abusing Smart::Comments extensively for many years,
> very handy.
> use Smart::Comments;
> my $var = 'blue';
> ### $var
> Then de-activate all print-outs with
> no Smart::Comments;
> Super handy. I avoid in-lining and create variables just to be able to
> implement print-outs with '###' whenever convenient.
> And we have a test that checks smart comments aren't enabled before
> shipping.
> On Sun, Jun 25, 2017 at 4:02 PM, Simon Green <mail at simon.green> wrote:
>> On 23/06/17 21:35, Peter Kelly wrote:
>> > Hi mongers,
>> >
>> > Could we have a round-the-room about IDEs?
>> Definitely vim for me. Maybe it's because I've been coding before IDEs
>> were around. And since Vim 7, tabs have made it even easier to have
>> multiple source code open in the one window.
>> And like others have said, 'print' (or 'say') statements are the best
>> form of debugging around. If I'm trying to track performance issues,
>> NYTProf is my go-to tool.
>> --
>> Simon
>> _______________________________________________
>> Wellington-pm mailing list
>> Wellington-pm at pm.org
>> http://mail.pm.org/mailman/listinfo/wellington-pm
> --
> _______________________________________________
> Wellington-pm mailing list
> Wellington-pm at pm.org
> http://mail.pm.org/mailman/listinfo/wellington-pm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/wellington-pm/attachments/20170626/d4bd8887/attachment.html>

More information about the Wellington-pm mailing list