On Friday 14 August 2009 16:18:38 Shawn H. Corey wrote:
> Shlomi Fish wrote:
> > My recent impression of most Perl programmers has been the opposite -
> > most of them have been too lazy or unmotivated to learn about the perl -d
> > flag (or similar interactive debuggers), and are always using prin
From: "Shawn H. Corey"
> I use Data::Dumper a lot, so most of my debugging statements have
> "Dumper" in them, making them easy to find. For those that don't, I add
> "# TEMPORARY" at the end. And I leave them behind; I just put a "#" in
> front of them. :)
I tend to not indent them. So they
> "Steve" == Steve Bertrand writes:
Steve> Interesting. So, print is a debugging tool that does a complete full
Steve> circle. Many on the list have helped me with using different debug
Steve> techniques which have greatly helped me advance my understanding of what
Steve> my code is actually
> "Steve" == Steve Bertrand writes:
SB> - what in God's name is Abigail's last name?
>>
>> '' (the answer to your question)
Steve> I knew pretty much for fact that this would be the answer, but honestly,
Steve> I wanted to know how you would write the empty string, without thinking
Steve> a
Chas. Owens wrote:
On Fri, Aug 14, 2009 at 10:20, Shawn H. Corey wrote:
snip
Komodo doesn't work on my machine and since it's propriety, I can't get its
source to compile it.
snip
Odd, it works just fine on my OS X box, my Linux box, and I hear it
works in MS Windows. You must be using a flav
Chas. Owens wrote:
On Fri, Aug 14, 2009 at 09:59, Shawn H. Corey wrote:
Chas. Owens wrote:
Are you using a visual debugger or a commandline debugger?
Command line, they didn't have visual debuggers back then. :)
snip
Why, back when I was a lad we had to debug things by checking the
[waveleng
On Fri, Aug 14, 2009 at 10:20, Shawn H. Corey wrote:
snip
> Komodo doesn't work on my machine and since it's propriety, I can't get its
> source to compile it.
snip
Odd, it works just fine on my OS X box, my Linux box, and I hear it
works in MS Windows. You must be using a flavor of BSD other tha
On Fri, Aug 14, 2009 at 09:59, Shawn H. Corey wrote:
> Chas. Owens wrote:
>>
>> Are you using a visual debugger or a commandline debugger?
>
> Command line, they didn't have visual debuggers back then. :)
snip
Why, back when I was a lad we had to debug things by checking the
[wavelength of the RF
Chas. Owens wrote:
Are you using a visual debugger or a commandline debugger? I find
this makes all of the difference in the world. Try downloading a
trial version of [Komodo IDE][1] or using [ddd][2]. I detest IDEs,
but visual debuggers are incredibly more useful than commandline
debuggers, a
Chas. Owens wrote:
Are you using a visual debugger or a commandline debugger?
Command line, they didn't have visual debuggers back then. :)
--
Just my 0.0002 million dollars worth,
Shawn
Programming is as much about organization and communication
as it is about coding.
I like Perl; it
On Fri, Aug 14, 2009 at 09:18, Shawn H. Corey wrote:
snip
> The last time I used a debugger was on a large C project. For small
> programs and unit testing, it was fine, but when things went over 2000
> lines, it became increasingly frustrating to use. Of course, print
> statements have their lim
Shlomi Fish wrote:
My recent impression of most Perl programmers has been the opposite - most of
them have been too lazy or unmotivated to learn about the perl -d flag (or
similar interactive debuggers), and are always using print's or going on IRC
asking "What is wrong with this code?" I find
On Fri, 14 Aug 2009 00:52:24 -0400, Chas. Owens wrote:
> I have seen the opposite: too many coders sticking with print instead of
> picking up a debugger when the situation called for one. I tend to
> debug with a combination of looking at the code, logs, and print
> statements, but a good visual
Chas. Owens wrote:
> On Fri, Aug 14, 2009 at 00:21, Uri Guttman wrote:
> snip
>> i started with punch cards. print was all you had besides thorough and
>> deep analysis of your code. that is a talent lost on too many coders
>> today. and even today proper use of print is better than any debug
>> to
Chas. Owens wrote:
> On Fri, Aug 14, 2009 at 00:21, Uri Guttman wrote:
> snip
>> i started with punch cards. print was all you had besides thorough and
>> deep analysis of your code. that is a talent lost on too many coders
>> today. and even today proper use of print is better than any debug
>> to
On Friday 14 August 2009 07:21:00 Uri Guttman wrote:
> > "SB" == Steve Bertrand writes:
> >> i don't use it but i know plenty who do and it seems to be a good
> >> idea. i would recommend it for most perl hackers and if you want to
> >> enforce a known set of coding styles. i strongly en
> "CO" == Chas Owens writes:
CO> On Fri, Aug 14, 2009 at 00:21, Uri Guttman wrote:
CO> snip
>> i started with punch cards. print was all you had besides thorough and
>> deep analysis of your code. that is a talent lost on too many coders
>> today. and even today proper use of print
On Fri, Aug 14, 2009 at 00:21, Uri Guttman wrote:
snip
> i started with punch cards. print was all you had besides thorough and
> deep analysis of your code. that is a talent lost on too many coders
> today. and even today proper use of print is better than any debug
> tool. but it is still a skill
Uri Guttman wrote:
>> "SB" == Steve Bertrand writes:
>
> SB> Uri Guttman wrote:
> >>
> >> i wish i could understand my comments better! :)
>
> SB> Your name came up in "Perl Best Practices" (along with many
> SB> others). You also made me realize that the use of $_ in a
> SB> pa
> "SB" == Steve Bertrand writes:
SB> Uri Guttman wrote:
>>
>> i wish i could understand my comments better! :)
SB> Your name came up in "Perl Best Practices" (along with many
SB> others). You also made me realize that the use of $_ in a
SB> particular code snip was not a good id
Chas. Owens wrote:
> On Thu, Aug 13, 2009 at 20:25, Steve Bertrand wrote:
> snip
>> - is "Perl Best Practises" what most of you use as general guidelines?
>> IOW, if I continue reading it, will you be able to better understand my
>> code (even though I stick with a few _small_ personal techniques)?
On Thu, Aug 13, 2009 at 20:25, Steve Bertrand wrote:
snip
> - is "Perl Best Practises" what most of you use as general guidelines?
> IOW, if I continue reading it, will you be able to better understand my
> code (even though I stick with a few _small_ personal techniques)? From
> what I've read so
Uri Guttman wrote:
>> "SB" == Steve Bertrand writes:
>
> SB> - is "Perl Best Practises" what most of you use as general guidelines?
> SB> IOW, if I continue reading it, will you be able to better understand my
> SB> code (even though I stick with a few _small_ personal techniques)? From
> "SB" == Steve Bertrand writes:
SB> - is "Perl Best Practises" what most of you use as general guidelines?
SB> IOW, if I continue reading it, will you be able to better understand my
SB> code (even though I stick with a few _small_ personal techniques)? From
SB> what I've read so far
24 matches
Mail list logo
