Lines Matching refs:code

18 code.
84   Vim development on that platform, and it doesn't mean messing up the code.
125 - The source code should not become a mess.  It should be reliable code.
130   too much platform-independent code.
131 - Use the object-oriented spirit: Put data and code together.  Minimize the
132   knowledge spread to other parts of the code.
163 These are the rules to use when making changes to the Vim source code.  Please
166 This list is not complete.  Look in the source code for more examples.
171 The basic steps to make changes to the code:
172 1. Get the code from github.  That makes it easier to keep your changed
173    version in sync with the main code base (it may be a while before your
178 3. Make the source code changes.
195 problems for existing patches.  Only use them for new and changed code.
200 for file and function headers and larger blocks of code, E.g.:
205 For new code or lines of code that change, it is preferred to use // comments.
206 Especially when it comes after code:
423 In general: Use empty lines to group lines of code together.  Put a comment
484   used by other code are much slower.  Myspell uses a hashtable, for example.