Linker Loader :
Link order of libraries ,
Link options for gcc ld,
Yolinux Tutorial on Static, Shared Dynamic and Loadable Linux Libraries,
Shared Library How-to,
How-to write Shared Libraries by Ulrich Drepper (Redhat),
Cross Platform Shared Library How-to ,
Program Library How-to,
Linkers and Loaders online downloadable book
Showing posts with label understanding. Show all posts
Showing posts with label understanding. Show all posts
Tuesday, October 26, 2010
Howto Look Inside Executables, Libraries and Object Files
Wednesday, October 6, 2010
Understand Source Code by Reading Code and Refactoring for Maintaining Large Projects
This list consists of one-liner tips to be used for easy lookup and reference.
Rewriting Code for Better Understanding (Coding Horror)
Rewriting Code for Better Understanding (Coding Horror)
- What I cannot create, I do not understand. [Richard Feynman]
- "What I do not create, I do not understand."[Chris]
- "It's easier to understand 600 tables than 100,000 lines of code." [PaulC on comp.databases.theory/2005]
- Create a new project with blocks of code copied from old code. Refactor to reduce "old code smell"
- Start refactoring by adding small tests to better understand code and act as regression tests.
- Just scan through huge amounts of code till it starts making sense - "understand by constant exposure".
- Create a text file to capture your understanding - briefly describe how the component works, realtions to other components, what it persists, its states, and source browsing/debugging tips you found useful.
- Manually reformat a copy of the code - white space, and indented as per your personal style.
- Working Effectively with Legacy Code
- Object Oriented Reengineering Patterns
- Refactoring: Improving the Design of Existing Code
Labels:
books,
code-reading,
coding-horror,
collection,
comments,
how-to,
maintainance,
projects,
refactoring,
software,
source-code,
stackoverflow,
strategies,
techniques,
tips,
understanding
Subscribe to:
Posts (Atom)