On Fri, 8 Dec 2000, Matt Sergeant wrote:
> fatalsToBrowser installs a $SIG{__DIE__} handler, and so prevents you from
> properly using eval{} blocks, or nice modules like Error.pm or
> Class::Exception (or whichever way around Dave has it this week :-)
That's Exception::Class. phhhbbtt!
-dave
> "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
Matt> On Fri, 8 Dec 2000, Bruce W. Hoylman wrote:
>>
>> use IO::File;
>> use CGI::Carp qw(carpout fatalsToBrowser carp);
Matt> Bye bye exception handling.
You mean eval{} block exception handling, or something else? W
On Fri, 8 Dec 2000, Bruce W. Hoylman wrote:
> > "Stas" == Stas Bekman <[EMAIL PROTECTED]> writes:
>
> >> Plus, I *always* use '-w' and '-T' and get them cleanly working
> >> during development phases, although I shut them off for actual
> >> deployment.
>
> Stas> 1. You cann
On Fri, 8 Dec 2000, Bruce W. Hoylman wrote:
> > "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
>
> Matt> On Fri, 8 Dec 2000, Bruce W. Hoylman wrote:
> >>
> >> use IO::File;
> >> use CGI::Carp qw(carpout fatalsToBrowser carp);
> Matt> Bye bye exception handling.
>
> Yo
> "Stas" == Stas Bekman <[EMAIL PROTECTED]> writes:
>> Plus, I *always* use '-w' and '-T' and get them cleanly working
>> during development phases, although I shut them off for actual
>> deployment.
Stas> 1. You cannot use -T under mod_perl, you should use
Stas>PerlT
On Fri, 8 Dec 2000, Bruce W. Hoylman wrote:
> > "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
>
> Matt> On Fri, 8 Dec 2000, Bruce W. Hoylman wrote:
> >>
> >> use IO::File;
> >> use CGI::Carp qw(carpout fatalsToBrowser carp);
> Matt> Bye bye exception handling.
>
>
> > "SB" == Stas Bekman <[EMAIL PROTECTED]> writes:
>
> SB> 2. 'PerlTaintCheck On' is a must in production!!! not development:
>
> Huh?!?!?!? It is a must always. You can't develop without it and
> then expect it to work with taint checking on at a later time.
Of course, sorry for being u
> "SB" == Stas Bekman <[EMAIL PROTECTED]> writes:
SB> 2. 'PerlTaintCheck On' is a must in production!!! not development:
Huh?!?!?!? It is a must always. You can't develop without it and
then expect it to work with taint checking on at a later time.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Plus, I *always* use '-w' and '-T' and get them cleanly working during
> development phases, although I shut them off for actual deployment.
1. You cannot use -T under mod_perl, you should use PerlTaintCheck
instead: http://perl.apache.org/guide/porting.html#Taint_Mode
2. 'PerlTaintCheck On' i
t;> debug. Mhhh. They must write 'perlfect' code, I guess, and/or
> >> understand those cryptic debuggers ...
>
> Dave> I just do a lot of debugging via warn statements and looking
> Dave> at the error logs.
>
> My BEGIN block looks like this.
>>>>> "Dave" == Dave Rolsky <[EMAIL PROTECTED]> writes:
Dave> On Thu, 7 Dec 2000, martin langhoff wrote:
>> I wonder how do those hardcore guys that develop using handlers
>> debug. Mhhh. They must write 'perlfect' code, I
using handlers debug.
> > Mhhh. They must write 'perlfect' code, I guess, and/or understand those
> > cryptic debuggers ...
>
> Do not be afraid of the command line...
>
> The Perl debugging shell is really not so hard if you give it a chance.
> I've taugh
martin langhoff wrote:
> I wonder how do those hardcore guys that develop using handlers debug.
> Mhhh. They must write 'perlfect' code, I guess, and/or understand those
> cryptic debuggers ...
>
Actually, debugging handlers is pretty easy. Just run httpd with the -X
On Thu, 7 Dec 2000, martin langhoff wrote:
> I wonder how do those hardcore guys that develop using handlers debug.
> Mhhh. They must write 'perlfect' code, I guess, and/or understand those
> cryptic debuggers ...
I just do a lot of debugging via warn statements and l
re guys that develop using handlers debug.
> Mhhh. They must write 'perlfect' code, I guess, and/or understand those
> cryptic debuggers ...
Personally I've always relied on sending debug messages to the log, and
then staring at the code for a few minutes/months.
--
/||
works. It's almost exactly the same as debugging a standard
script.
> I wonder how do those hardcore guys that develop using handlers debug.
> Mhhh. They must write 'perlfect' code, I guess, and/or understand those
> cryptic debuggers ...
Do not be afraid of the c
On Thu, 7 Dec 2000, martin langhoff wrote:
> [1] Having grown up in a cushioned, fancy VB 3.0 IDE, I still
> find both vi, emacs and textmode debug too harsh for me.
You could try ptkdb or DDD for GUI debugging.
- Perrin
-
I guess, and/or understand those
cryptic debuggers ...
martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Thu, 7 Dec 2000, martin langhoff wrote:
> All this talk about DDD is making me wonder if there is a suitable
> (graphical) Perl IDE that I can run on Gnome.
Last time I tried them, I found ptkdb a bit nicer than DDD, mostly because
DDD was kind of slow. I don't know how easy it is to ma
Perrin,
In fact, I've always been coding from NT machines -- for my *nix
servers, of course. Now the ActiveState people are building a
cross-platform and cross-language IDE that integrates with perldebug
nicely -- or so it seems. I'm actually starting to like it -- it's built
on top of mo
20 matches
Mail list logo
