suspect-devices/circuitpython/py/objtuple.h, branch v1.9.3CircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.9.32017-08-29T03:16:30+00:00all: Convert mp_uint_t to mp_unary_op_t/mp_binary_op_t where appropriate2017-08-29T03:16:30+00:00Damien Georgedamien.p.george@gmail.com2017-08-29T03:04:01+00:00urn:sha1:58321dd9854d71a96e5db2d361e0efc05d9de8cf
The unary-op/binary-op enums are already defined, and there are no
arithmetic tricks used with these types, so it makes sense to use the
correct enum type for arguments that take these values. It also reduces
code size quite a bit for nan-boxing builds.
all: Use the name MicroPython consistently in comments2017-07-31T08:35:40+00:00Alexander Steffendevel.20.webmeister@spamgourmet.com2017-06-30T07:22:17+00:00urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e
There were several different spellings of MicroPython present in comments,
when there should be only one.
all: Unify header guard usage.2017-07-18T01:57:39+00:00Alexander Steffendevel.20.webmeister@spamgourmet.com2017-06-29T21:14:58+00:00urn: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
py: Add iter_buf to getiter type method.2017-02-16T07:38:06+00:00Damien Georgedamien.p.george@gmail.com2016-01-09T23:14:54+00:00urn:sha1:ae8d86758631e62466a55d179897d2111c3cb1c1
Allows to iterate over the following without allocating on the heap:
- tuple
- list
- string, bytes
- bytearray, array
- dict (not dict.keys, dict.values, dict.items)
- set, frozenset
Allows to call the following without heap memory:
- all, any, min, max, sum
TODO: still need to allocate stack memory in bytecode for iter_buf.
py/objtuple: Convert mp_uint_t to size_t where appropriate.2017-02-16T05:51:16+00:00Damien Georgedamien.p.george@gmail.com2017-02-16T05:09:51+00:00urn:sha1:229823942c79b1233c43dc155bae01c20a8cec57py: Add MP_ROM_* macros and mp_rom_* types and use them.2015-11-29T14:25:04+00:00Damien Georgedamien.p.george@gmail.com2015-11-27T13:38:15+00:00urn:sha1:cbf7674025814797f5c537d6d1c195efe58ccaafpy: Add attrtuple object, for space-efficient tuples with attr access.2015-04-21T14:14:24+00:00Damien Georgedamien.p.george@gmail.com2015-04-21T14:14:24+00:00urn:sha1:5aa311d33084c24262780cae0a65d748990ce7e1
If you need the functionality of a namedtuple but will only make 1 or a
few instances, then use an attrtuple instead.
py: Overhaul and simplify printf/pfenv mechanism.2015-04-16T14:30:16+00:00Damien Georgedamien.p.george@gmail.com2015-04-09T22:56:15+00:00urn: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.
py: Move to guarded includes, everywhere in py/ core.2015-01-01T20:32:09+00:00Damien Georgedamien.p.george@gmail.com2015-01-01T20:27:54+00:00urn:sha1:51dfcb4bb7613ed164952712d9a5235a7b833cde
Addresses issue #1022.
Change some parts of the core API to use mp_uint_t instead of uint/int.2014-08-29T23:35:11+00:00Damien Georgedamien.p.george@gmail.com2014-08-29T23:35:11+00:00urn:sha1:ecc88e949ca5e307d22da4605a40d39ea2df9e3b
Addressing issue #50, still some way to go yet.