CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=2.2.4 2017-07-18T01:57:39+00:00 2017-07-18T01:57:39+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-29T21:14:58+00:00 urn:sha1:299bc625864b9e624ed599c94a5f95870516139a The code conventions suggest using header guards, but do not define how those should look like and instead point to existing files. However, not all existing files follow the same scheme, sometimes omitting header guards altogether, sometimes using non-standard names, making it easy to accidentally pick a "wrong" example. This commit ensures that all header files of the MicroPython project (that were not simply copied from somewhere else) follow the same pattern, that was already present in the majority of files, especially in the py folder. The rules are as follows. Naming convention: * start with the words MICROPY_INCLUDED * contain the full path to the file * replace special characters with _ In addition, there are no empty lines before #ifndef, between #ifndef and one empty line before #endif. #endif is followed by a comment containing the name of the guard macro. py/grammar.h cannot use header guards by design, since it has to be included multiple times in a single C file. Several other files also do not need header guards as they are only used internally and guaranteed to be included only once: * MICROPY_MPHALPORT_H * mpconfigboard.h * mpconfigport.h * mpthreadport.h * pin_defs_*.h * qstrdefs*.h 2016-11-01T23:16:35+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-11-01T22:47:03+00:00 urn:sha1:5fae91432646637c4f8d10c6102b76068f889226 Size 64 was incorrect and will lead to stack corruption. Size 88 was verified empirically. Also, allow to skip defining it if MD5_CTX preprocessor macro is already defined (to avoid header conflict). 2016-11-01T23:16:20+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-11-01T22:41:51+00:00 urn:sha1:2ec70dc812035bf3a2af2c1f024206e97d606d45 2016-10-23T13:43:07+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-10-23T13:43:07+00:00 urn:sha1:b6c22c42abe23560c9452511168c158d5cc8fe4c 2016-09-03T17:45:11+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-09-03T17:45:11+00:00 urn:sha1:015774a04faa50708ce3692dc3748989e19e98e9 2016-08-03T21:29:19+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-08-03T21:29:19+00:00 urn:sha1:e33d2383d1ed4805583e6562b2f47e018457e854 Requires firmware generated by the latest makeimg.py (which stores size and md5 of the firmware together with the firmware itself). 2016-05-02T21:35:11+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-02T21:35:11+00:00 urn:sha1:76c81cd5a631f2329a4ec7a5cb53632eae017af4 Useful for testing fragmentation issues in OS heap. E.g. freemem() may report large amount, but is it possible to actually allocate block of a given size? Issue malloc() (followed by free()) to find out. 2016-03-29T07:29:57+00:00 Damien George damien.p.george@gmail.com 2016-03-29T07:29:57+00:00 urn:sha1:6ca17c19225c228c39dcc1f8be4ec269c702a165 Uses what is suspected to be a hardware random number generator. 2016-03-05T19:56:32+00:00 Damien George damien.p.george@gmail.com 2016-03-01T09:20:22+00:00 urn:sha1:077448328a42e732c1ae3a063670b71914ed489c 2016-03-04T17:39:24+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-04T17:39:24+00:00 urn:sha1:f22a4f8e0ac206b39cf76d697b890581cb55abbc