in reply to RE: RE: #!/usr/bin/perl -w
in thread #!/usr/bin/perl -w
> It's just a warning, but it's a good sign that you're not quite done programming yet. :)
You mean there's a point at which one's done programming? Gee, and I always thought the client would call again tomorrow asking for something else to be included! <snicker>
Seriously, I have found that one of the main reasons to use -w is not for immediate benefit as chromatic's post might suggest, but it keeps you from having to figure out issues later on when you come back to maintain the code. Its a win-win situation: safer now, and better later...
#!/home/bbq/bin/perl
# Trust no1!
You mean there's a point at which one's done programming? Gee, and I always thought the client would call again tomorrow asking for something else to be included! <snicker>
Seriously, I have found that one of the main reasons to use -w is not for immediate benefit as chromatic's post might suggest, but it keeps you from having to figure out issues later on when you come back to maintain the code. Its a win-win situation: safer now, and better later...
#!/home/bbq/bin/perl
# Trust no1!
|
---|
Replies are listed 'Best First'. | |
---|---|
RE: (bbq) RE: RE: RE: #!/usr/bin/perl -w
by chromatic (Archbishop) on Oct 05, 2000 at 07:40 UTC |
In Section
Seekers of Perl Wisdom