<div dir="ltr">What makes the Micro Python board more attractive than the BeagleBone Black, which is just as open, and orders of magnitude more capable? I understand the appeal of targeting really tiny hardware like 8-bit microcontrollers, but I don't understand the appeal of this middle-of-the-road board. But I may be missing something.<div>
<br></div><div> Bob</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 23, 2013 at 8:27 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2013-12-23, at 15:02, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br>
<div class="im"><br>
> 2013/12/23 Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>><br>
>> don't be surprised if the fallback code suffers from bitrot. It is never executed on regular VMs with all the primitives in place. Having recently implemented a minimal VM I did discover those bugs ;)<br>
><br>
> Yep, I saw at least one when I failed to change some primitive and made it accidentally fail.<br>
> For better testability, we could isolate the fallback code under a separate method, but that would consume a bunch of selectors and somehow be contradictory with a principle of economy - less is more.<br>
<br>
</div>For testing you could temporarily set the CompiledMethod's primitive index to 0.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Bert -<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>