Lines Matching refs:code

10 The biggest time sink in code development is generally the cycle of
34   source code where the compiler detects an error, even when not
55 Most code development for PETSc codes should be done on one processor;
77 - Leave space in the code to make it readable.
78 - Line things up in the code for readability. Remember that any code
82 - Realize that you **will** have to debug your code. **No one** writes
83   perfect code, so always write code that may be debugged and learn how
86 - **Never** hardwire a large problem size into your code. Instead,
90   code.
91 - Develop your code on the simplest machine to which you have access.
93   write and initially test all our code on laptops or workstations
97   PETSc code is completely portable, switching to a parallel machine
99   logging into another machine -- there are no code or makefile
101 - Never develop code directly on a multi-node computing system; your