<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/tests/micropython/heapalloc_exc_raise.py, branch 6.0.x</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.0.x</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.0.x'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2017-12-11T10:00:41+00:00</updated>
<entry>
<title>tests/heapalloc_*: Refactor some tests to work in strict stackless mode.</title>
<updated>2017-12-11T10:00:41+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2017-12-11T09:56:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=e02cb9ec318580497dbb17f369a61d9e932094e5'/>
<id>urn:sha1:e02cb9ec318580497dbb17f369a61d9e932094e5</id>
<content type='text'>
In strict stackless mode, it's not possible to make a function call with
heap locked (because function activation record aka frame is allocated on
heap). So, if the only purpose of function is to introduce local variable
scope, move heap lock/unlock calls inside the function.
</content>
</entry>
<entry>
<title>tests/heapalloc_exc_raise.py: Heap alloc test for raising/catching exc.</title>
<updated>2017-02-20T01:22:32+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2017-02-20T01:22:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=6fc6f10b1ec61ecaa1c72ed767a41fbf5bacaac9'/>
<id>urn:sha1:6fc6f10b1ec61ecaa1c72ed767a41fbf5bacaac9</id>
<content type='text'>
</content>
</entry>
</feed>
