On 03/04/2003 00:09:27 Daniel Gross wrote: >Thank you for the incoming IDE suggestions ... > >Its interesting to see that some Perl developers seem not to "require" >an interactive debugging environment, but are happy with power-text >editors, and (I would imagine) with the command line debugger. My >assumption was that an IDE with integrated debugging facilities would be >a big help during the code writing & testing cycles ... > >
IMO, integrated debuggers are overrated (although "Edit and continue" is neat). Any decent OS capable of running more than one program allows a separate command window to launch/debug your script. If you don't like the commandline debugger, there's Devel::ptkdb. But Perl's built-in debugger is usable even for GUI-dependent types like myself :-) Is there a console-based debugger front-end ? (perhaps in curses or suchlike) A development environment MUST have: 1) Some kind of make integration, i.e. it has to capture the output of the build and offer the ability to open the editor at the line of the error. In case of Perl there's no "build" as such, but running "perl -c" after you edited the script catches typos early. 2) Keyword help, i.e. launching WinHelp, man, perldoc, etc., and pass the word under the cursor. This is why I use FTE (http://fte.sourceforge.net/) A development environment SHOULD have: 1) Syntax highlighting editor. 2) Editor with parens/brace matching ability 3) Source browsing or tags support 4) Some kind of macro language or programmability 5) Editable keybindings (I cannot use any editor which doesn't Save on F2, too much Borland :-) -- Csaba Ráduly, Software Engineer, Sophos Anti-Virus Email: [EMAIL PROTECTED], Tel: 01235 559933, Web: www.sophos.com Add live virus info to your website: http://www.sophos.com/link/vfeed _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
