forever PRINT still the most powerful debugger
-
Currently I'm working in a PHP project , My experience with PHP 2 months ago was zero, add to this that we used to use MS products about 6 years, The problem that I face now is that I have no running debugger for our project so in this situation like always I insert PRINT after every snippet of code and trace the output of PRINT for debugging, I'm enjoying PRINT:laugh:. Mahmoud Zidan
(well, not as much, at least) ;P
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
Currently I'm working in a PHP project , My experience with PHP 2 months ago was zero, add to this that we used to use MS products about 6 years, The problem that I face now is that I have no running debugger for our project so in this situation like always I insert PRINT after every snippet of code and trace the output of PRINT for debugging, I'm enjoying PRINT:laugh:. Mahmoud Zidan
Chuck Norris wouldn't use a debugger. He would just roundhouse kick the code into submission.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Yeah! I output my debug stuff to a parallel port where it's displayed as binary on LEDs. (I just can't escape my mainframe days - many, many years ago)
-
Currently I'm working in a PHP project , My experience with PHP 2 months ago was zero, add to this that we used to use MS products about 6 years, The problem that I face now is that I have no running debugger for our project so in this situation like always I insert PRINT after every snippet of code and trace the output of PRINT for debugging, I'm enjoying PRINT:laugh:. Mahmoud Zidan
There are people who just don't see any value in a debugger. When I asked for a decent JavaScript debugger a couple of years ago, the universal answer was: "just use alert" :)
-
(well, not as much, at least) ;P
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
That's about the only time you should ever need it. ;)
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
Thats why he using PRINT and INPUT, actually a system I'm converting here runs on unix and the only way to debug is to use printf() and getchar() :wtf:
.net is a box of never ending treasures, every day I get find another gem.
That just brought back nightmares of coding c on UNIX. Blue telnet screens and printf(), lots of coffee and late nights, err early mornings rather.
-
That's about the only time you should ever need it. ;)
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
In my modern programming environment I just use an integrated debugger, I can step in code, set breakpoints and watch variables, is all so easy, one reason why I don't use PHP.
.net is a box of never ending treasures, every day I get find another gem.
norm .net wrote:
In my modern programming environment I just use an integrated debugger
This is sometimes difficult, even if the debugger supports embedded/remote mode. In live-environments, where data is coming in steady streams, the best way is still a super-print debugging. I stream a debug network socket to another computer (or monitor) with a steady stream of organized data. It is strongly resembling some of the modern debuggers, but works remotely and without interrupting the data stream. Since the input and GUI are on different threads, you can even stop the screen update without affecting the debug stream in background and then start watching again. Not quite as good as break points, but break points don't always help when breaking the data flow causes more problems than it helps.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
That just brought back nightmares of coding c on UNIX. Blue telnet screens and printf(), lots of coffee and late nights, err early mornings rather.
