CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=5.3.x 2016-02-14T22:16:46+00:00 2016-02-14T22:16:46+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-14T22:16:46+00:00 urn:sha1:6b0c88256b03de63280eb7b704f5b6aaa5e9cc46 2016-02-14T17:15:22+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-14T15:43:51+00:00 urn:sha1:e3c66a5a675a91810ca9c1874ba706dced6036ec 2016-02-14T17:15:22+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-14T14:22:11+00:00 urn:sha1:baf47c84c40611943b8693303d3025537752a04c 2016-02-06T23:25:28+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-06T19:05:43+00:00 urn:sha1:ab0e36b3dac042cdc43c0e6ae5283c4d2154f960 If MICROPY_VFS_FAT is defined, mp_type_fileio & mp_type_textio won't be defined, as these may be alredy defined elsewhere. The idea is to have compartmentalized VFS FatFs class, which can work in parallel with some other "main" filesystem. E.g., for unix port, mp_type_fileio, etc. will be defined for the main POSIX filesystem, while stmhal/file.c will be a self-contained VFS file class. 2016-02-06T23:25:28+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-06T19:02:34+00:00 urn:sha1:350ab0f570a2cc570ceb9facb38cbd9ce68057f3 Move definition of mp_builtin_open_obj to a separate module, then file.c becomes more or less compartmentalized FatFs file class, which can be used together with file class implementations for other (V)FSes. 2016-01-11T00:49:27+00:00 Damien George damien.p.george@gmail.com 2016-01-03T15:55:55+00:00 urn:sha1:5b3f0b7f39bd67cc9182993c288f09f67a0890df The first argument to the type.make_new method is naturally a uPy type, and all uses of this argument cast it directly to a pointer to a type structure. So it makes sense to just have it a pointer to a type from the very beginning (and a const pointer at that). This patch makes such a change, and removes all unnecessary casting to/from mp_obj_t. 2015-08-13T21:56:32+00:00 blmorris bryan.morrissey@gmail.com 2015-08-04T23:45:30+00:00 urn:sha1:bdd78c31b68db5323796d93e0a17159806ce10fc 2015-05-24T13:07:11+00:00 Dave Hylands dhylands@gmail.com 2015-05-22T03:16:42+00:00 urn:sha1:968b7dd173d58d917c18dfa7706087db2abcfa6c 2015-04-16T14:30:16+00:00 Damien George damien.p.george@gmail.com 2015-04-09T22:56:15+00:00 urn:sha1:7f9d1d6ab923096582622b700bedb6a571518eac Previous to this patch the printing mechanism was a bit of a tangled mess. This patch attempts to consolidate printing into one interface. All (non-debug) printing now uses the mp_print* family of functions, mainly mp_printf. All these functions take an mp_print_t structure as their first argument, and this structure defines the printing backend through the "print_strn" function of said structure. Printing from the uPy core can reach the platform-defined print code via two paths: either through mp_sys_stdout_obj (defined pert port) in conjunction with mp_stream_write; or through the mp_plat_print structure which uses the MP_PLAT_PRINT_STRN macro to define how string are printed on the platform. The former is only used when MICROPY_PY_IO is defined. With this new scheme printing is generally more efficient (less layers to go through, less arguments to pass), and, given an mp_print_t* structure, one can call mp_print_str for efficiency instead of mp_printf("%s", ...). Code size is also reduced by around 200 bytes on Thumb2 archs. 2015-03-04T20:35:41+00:00 Damien George damien.p.george@gmail.com 2015-03-04T20:35:41+00:00 urn:sha1:4f94d90d4dba522a2fcf451da9c78e810782e2c0 This helps make files reusable across other ports.