>>>>> "RJB" == Richard J Barbalace <[EMAIL PROTECTED]> writes:

  RJB> Hi.
  RJB> Quoting Uri Guttman <[EMAIL PROTECTED]>:
  >> <old fart rant>
  >> i use print for debugging (even in complex multiprocess
  >> systems via log files) as i know where and what to print from
  >> experience. setting up a debugger to stop at the right place and only
  >> print the right things is much more work IMO.

  RJB> That should not be true anymore.  In my IDE (eclipse), to get the
  RJB> debugger to stop at the right place and display the right
  RJB> information, I just double-click next to the line; that is a lot
  RJB> faster and easier than even typing "print".  It also means that I
  RJB> do not have to undo extraneous code or diff against my SVN
  RJB> repository verify that I have cleaned up any additions made for
  RJB> testing.  And if I decide I need to check some other data or
  RJB> expression in the middle of a debug run, I can do that with a
  RJB> single click.  To set up and run the debugger, I just click the
  RJB> debug icon.

what is this click thing you speak of??

  RJB> Perhaps the real problem here is that there are too many "old farts" who 
have
  RJB> not experienced a modern IDE and what it can offer.  In addition to easy
  RJB> debugging, just a few of the useful features to expect are:
  RJB> 1) highlighting of code, comments, TODOs, errors, etc.

i can read code just fine. too many colors burn my retina.

  RJB> 2) rollover documentation (displaying the docs for a function
  RJB> just by rolling the mouse over itsr name anywhere in the code)

i rarely need to read up on builtin functions. just part of my skill
set. and perldoc -f is fine for me to type when i need it. i still use
my perl pocket reference for some regex features from time to time.

  RJB> 3) highlighting of references (highlighting, say, a selected
  RJB> variable name everywhere in the code)

searching for a string in emacs highlights all occurances. big deal.

  RJB> 4) refactoring across files and projects (so if you change the name of a
  RJB> function or variable, replacement everywhere happens
  RJB> automatically)

i try to choose good names to begin with as part of the architecture and
design. doing a global grep replacement is easy enough with many tools.

  RJB> 5) links within source code (clicking through the name of a function
  RJB> automatically opens its file and jumps you to its definition)

tags files can do that. i don't use them either. not a problem in many
cases. moby code bases that need that are a mess in so many other ways.

  RJB> 6) outlining of files (including moving whole blocks of code
  RJB> w/drag-and-drop)

so??

  RJB> 7) file management, including automatic refactoring when moving files

refactoring is not just moving text around. where is the analysis help
in understanding the real goal of the system? sorry, ide's don't have AI
yet.

  RJB> 8) seamless integration with version control

emacs has that. big deal. most editors do.

  RJB> 9) spell-checking and warnings of many types

use strict.

  RJB> 10) searching of code across projects, documentation, and the web
  RJB> for anything

i have that in a Module::Build thing i did. works fine for me.

  RJB> None of these should require any setup or effort.

and none should with any decent editor. the IDE is just a nice toy for
those who need/want it. it isn't a silver bullet (read the mythical man
month for that). like any tool it is only as effective as its user.

  RJB> Sure, you can write fine code with just a text editor, but it
  RJB> might not be as easy, fast, or efficient as with an IDE.  It
  RJB> would be nice if there were a good one for Perl....

fast? efficient? in run time or design time? i will out up either of
mine against most typical coders with the best IDE they can afford. the
human aspect is still the key here. if you are whining about not having
a good ide for perl then why are you using perl? java has great ides and
largest number of moron coders. perl has better coders it seems but
poorer ides. maybe perl is a better ide on its own than java?

you can't hire good perl coders these days cause they all seem to have
jobs. that is why there are so many more jave resumes and such out
there. :)

uri

-- 
Uri Guttman  ------  [EMAIL PROTECTED]  -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org
 
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm

Reply via email to