> -----Original Message----- > From: Mike Ni [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 16 March 2004 3:46 PM > To: [EMAIL PROTECTED] > Subject: Perl -d > > Hey everyone, > > > While I was playing with perl's built-in debuger > (perl -d), I notice that debugger doesn't seem > care too much about whether a variable is declared? > > For example, I would get response of "empty hash" if > I do a "x \%dummy" regardless dummy hasn't been > delcared yet. > > The same response "empty hash" if I dump a declred > hash before it is initialize. > > It is as if there isn't too much difference between an > undeclared variable & unitialized variable? > > Is this the way it is ? Or I am not doing right? > > Thanks > Mike
Once the compilation phase has completed, and you are in the debugger, it is almost as if 'use warnings' and 'use strict' no longer apply to variable references. Hence you are free to create or access previously undefined, undeclared and unreferenced variables. Cheers. David -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
