diff options
| author | garyd9 <garyd9@hotmail.com> | 2018-01-03 13:28:35 +0300 |
|---|---|---|
| committer | dc42 <dcrocker@eschertech.com> | 2018-01-03 13:28:35 +0300 |
| commit | 518dc0e7c8744d32631a5a0c15fcaadaa241a807 (patch) | |
| tree | 733dc8e9fa8bc58b8d1996f3b04cf7bbff4f56ae /README.md | |
| parent | e0cd28423c2a47eae42178aa07b907b612e56e85 (diff) | |
Update README.md (#152)
fix minor typo
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -14,7 +14,7 @@ General design principles of RepRapFirmware: * Unlike most other 3D printer firmwares, it is not intended to be run on outdated 8-bit processors with limited CPU power and RAM. So make good use of the power of modern inexpensive ARM processors to implement advanced features. The minimum specification processor it is intended for is ARM Cortex M3 with 96Kb RAM such as the SAM3X8E. * "One binary to rule them all". For a given electronics board, all features of interest to most 3D printer owners are supported by a single binary. Users do not need to recompile the firmware unless they have unusual requirements. -* "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. +* "G-code everywhere". All firmware configuration is done using gcodes in the config.g file. Most types of changes 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 during normal operation, use it only during the initialisation and configuration phases. 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. |