CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.0.0-alpha.0 2017-08-26T02:17:07+00:00 2017-08-26T02:17:07+00:00 Dan Halbert halbert@halwitz.org 2017-08-26T02:17:07+00:00 urn:sha1:ef61b5ecb59e9b4e37e3e3c023c62d583c23eb16 cpx build compiles and loads and works in repl; test suite not run yet esp8266 not tested yet 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2017-07-23T19:32:05+00:00 Dan Halbert halbert@halwitz.org 2017-07-23T19:32:05+00:00 urn:sha1:f91493c97e20eef1d39a9cdc6c42a25cfd511734 Add max stack usage tracking, visible via debug module ustack. Add separate cpp flag for enabling modules: MICROPY_DEBUG_MODULES 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-03-07T07:12:24+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-13T13:43:28+00:00 urn:sha1:1d5d4f49d9bf7dd4930a2b00a0ce2ee7ffbbd604 Useful for embedded targets with fixed stack layout. 2015-01-01T20:32:09+00:00 Damien George damien.p.george@gmail.com 2015-01-01T20:27:54+00:00 urn:sha1:51dfcb4bb7613ed164952712d9a5235a7b833cde Addresses issue #1022. 2014-12-10T18:05:42+00:00 Damien George damien.p.george@gmail.com 2014-12-10T18:05:42+00:00 urn:sha1:b4fe6e28eb3bbf70b1f1da08a13a40a4ac3ee1db 2014-08-30T13:59:21+00:00 Damien George damien.p.george@gmail.com 2014-08-30T13:59:21+00:00 urn:sha1:4abff7500fb05430a2ce952a2430d4d0ba16047e Part of code cleanup, working towards resolving issue #50. 2014-06-30T23:14:08+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2014-06-30T23:13:42+00:00 urn:sha1:caa7334141e6d67ab6f3064b250e6729095ae56c 2014-06-26T21:03:55+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2014-06-25T00:03:34+00:00 urn:sha1:23668698cba9bf861c697e65e3d07f9433396b8b Such mechanism is important to get stable Python functioning, because Python function calling is handled with C stack. The idea is to sprinkle STACK_CHECK() calls in places where there can be C recursion. TODO: Add more STACK_CHECK()'s.