diff options
| author | dc42 <dcrocker@eschertech.com> | 2017-03-25 13:32:10 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-25 13:32:10 +0300 |
| commit | fb9583e82f14d32965f4d72376b10fd0a0c07ddc (patch) | |
| tree | 565b9a6b07905122bb16023e3d14581ace3e7d7e /README.md | |
| parent | c9ca46f5417404479064fc821d7d9eefcd5349c9 (diff) | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -7,7 +7,7 @@ General design principles: * "G-code everywhere". All firmware configuration is done using gcodes in the config.g file. Most type of change can be done on the fly so that you can experiment with different configurations without even having to restart the printer. * Use high-integrity coding standards to help ensure that the firmware is reliable. In particular, don't use dynamic memory allocation after the initialisation phase. The MISRA-C++ 2008 coding standard serves as a guide as to what is acceptable practice, but compliance to it is not rigidly enforced in order to allow features from later versions of the C++ language to be used. * Use an appropriate degree of modularity. Too little modularity makes the code hard to understand and maintain. Too much makes it hard to introduce new features when the existing module boundaries turn out to be inappropriate. -* Use object-based and object-oriented design principles where it is appropriate. In particular, class data should normally be private. Use 'friend'# sparingly or not at all. +* Use object-based and object-oriented design principles where it is appropriate. In particular, class data should normally be private. Use 'friend' sparingly or not at all. RepRapFirmware has pioneered a number of advances in 3D printing including: |