My Opera is closing 3rd of March

Something for Linux,Debian,Programming,Networks and Web

ВЯРВАЙ В НЕВЪЗМОЖНОТО И ДОКАЖИ ,ЧЕ Е ВЪЗМОЖНО! РОДЕН СЪМ ДА ТЕ ПОЗНАЯ И НАРИЧАМ ТЕ СВОБОДА! САМО МИСЛЕЩИЯТ ЧОВЕК Е СВОБОДЕН И НЕЗАВИСИМ!

Subscribe to RSS feed

Compiler and tools tricks

Textbooks are full of good advices:
Use other aids as well. Explaining your code to someone else (even a teddy bear) is wonderfully effective. Use a debugger to get a stak trace. Use some of the commercial tools that check for memory leaks, array bounds violations, suspect code and the like. Step through your program when it has become clear that you have the wrong picture of how the code works.
— Brian W. Kernighan, Rob Pike, The practice of programming, 1999 (Chapter 5: Debugging)

Enable every optional warning; view the warnings as a risk-free, high-return investment in your program. Don't ask, "Should I enable this warning?" Instead ask, "Why shouldn't I enable it?" Turn on every warning unless you have an excellent reason not to.
— Steve Macguire, Writing solid code, 1993

Sounds familiar? But with which option? This page tries to answer that kind of question.

http://www.fortran-2000.com/ArnaudRecipes/CompilerTricks.html
February 2014
M T W T F S S
January 2014March 2014
1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28