Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: Activestate Perl and the Komodo IDE

by trs80 (Priest)
on Oct 15, 2002 at 18:31 UTC ( #205455=note: print w/replies, xml ) Need Help??


in reply to Activestate Perl and the Komodo IDE

My first reply was strictly based on Komodo as a product, but I think your real question deserves some additional comments as well.

I am always on the quest for more consistent and faster to produce code. When I was managing other developers this seemed even more important, but I feel that most of this comes back to the individual doing the coding. Tools can no doubt help, but I find that the editor or IDE can only go so far. The biggest improvement for me when using a product like Komodo is its error highlighting, this has kept me from having to do a compile to find out I made a mistake, and I do feel my level of output has increased because of it. However I feel my coding method and quality has increased more by adding durable testing code and processes to the development cycle.

With your current tool set (cvs,emacs) I don't think you will get a large enough advantage out of Komodo, but I am not sure which feature in Komodo is most attractive to you.

See Ovid's recent node on testing , and my reply for more info.

If you are already using testing code then I would suggest that you look at how to move more of the code into rules or configuration files rather then keeping it all in code, this has been a big help in my development cycle as well. I like using Config::Auto along with Class::Accessor to create method calls for each of my configuration values which goes a long way in providing a flexible consistent means of getting and setting application parameters. This is all OO Perl and if you are not doing OO Perl I am not sure how to best bend it to your needs.

  • Comment on Re: Activestate Perl and the Komodo IDE

Replies are listed 'Best First'.
Re^2: Activestate Perl and the Komodo IDE
by Karel Capek (Initiate) on Dec 22, 2004 at 18:41 UTC
    This comment addresses Komodo 3.0.1.

    Two small problems I've noticed:

    the occasionally disappearing variables in the Output tab, which can be worked around by setting the variable names in the Watch tab;

    the continually resetting iterator, which occurs when one has a breakpoint set inside a foreach loop on a hash, for example. After puzzling over this for awhile I tried this with the Simpsons/Jetsons example from O'Reilly, and if a breakpoint is set in the loop, one gets a continuous stream of Simpsons, that never stops, even if -

    problem #3 - one presses the ineffective pause or the stop buttons. If no breakpoint, works fine.

    Actually, it appears the pause and stop buttons are ineffective whether or not breakpoints are used. It didn't appear that anyone else noticed these items, hence this comment. Plus, it's easier to login to Perlmonks than to jump through the various ActiveState bug reporting hoops.

    It's entirely possible I've done these operations improperly, but it doesn't appear so at this time.

    Thoughts for today:
    1) Engineers are pessimists; would you want to fly in a plane designed by an optimistic engineer?
    2) One cannot pleasantly surprise an optimist. Optimists, therefore, have only an unending series of disappointments that they will, of course, look forward to.

    Enjoy a safe and happy holiday season, keeping in mind that more people die on Christmas day than any other day.

    Have another day!

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://205455]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (8)
As of 2020-07-13 15:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?