CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=2.3.1 2017-08-21T11:34:23+00:00 2017-08-21T11:34:23+00:00 Damien George damien.p.george@gmail.com 2017-08-21T11:34:23+00:00 urn:sha1:4ec803a42ae3080d4af959c7c2edf81e57f79377 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 2017-07-12T02:51:37+00:00 Damien George damien.p.george@gmail.com 2017-07-12T02:51:37+00:00 urn:sha1:f1d260d878105bfbf25c0bb68da6190e35fc106a The default frozen modules are no longer included (but users can still specify their own via FROZEN_MPY_DIR), complex numbers are disabled and so are the native, viper and asm_thumb emitters. Users needing these features can tune the build to disable other things. 2017-06-28T05:45:04+00:00 Damien George damien.p.george@gmail.com 2017-06-28T05:45:04+00:00 urn:sha1:346f5d4cce8c536a881646be0ba55fe853ecb259 2017-06-28T05:12:04+00:00 Damien George damien.p.george@gmail.com 2017-06-23T05:53:12+00:00 urn:sha1:ebfdd96cb2332101a7a71f93214fb70959dea824 By default the firmware is built with single-precision floating point. To build a particular board using double precision instead, put the following line in the mpconfigboard.mk file: FLOAT_IMPL = double 2017-06-22T06:20:22+00:00 Damien George damien.p.george@gmail.com 2017-06-22T06:20:22+00:00 urn:sha1:b19138e82e32c512a8b9253519526ec1dc786378 2017-06-14T04:47:53+00:00 Damien George damien.p.george@gmail.com 2017-06-14T04:47:53+00:00 urn:sha1:c064f0a36a69b7479e7b828b97fed40b60247188 The default for the GIL is to enable it if threading is enabled, and this is the recommended way to use threading with the stmhal port. 2017-06-01T06:02:49+00:00 Damien George damien.p.george@gmail.com 2017-06-01T05:43:20+00:00 urn:sha1:6ff0ecfffcea4e7aa6301c54870ae97aa4a0cf72 2017-04-22T05:12:48+00:00 Damien George damien.p.george@gmail.com 2017-04-22T05:09:15+00:00 urn:sha1:03053f82db8fb79e8f62524948ebc2331c957af8 Prior to making this a config option it was previously available on these (and all other) ports, and it makes sense to keep it enabled for mpy-cross as well as ports that have a decent amount of space for the code. 2017-04-11T03:12:54+00:00 Damien George damien.p.george@gmail.com 2017-04-11T03:12:54+00:00 urn:sha1:9156c8b460a4b013312466744b47bc4bb5506269