4 ms·
It would make for some interesting modules in the mostly barren lib folder Yes, I think that's where p14p will suddenly become very useful (like the Arduino) -
by angusgr 16y ago
It would make for some interesting modules in the mostly barren lib folder
Yes, I think that's where p14p will suddenly become very useful (like the Arduino) - big libraries of (native code) hardware support easily strung together with developer-friendly Python code.
That's what I wanted to do with the Teensy++ (flesh out the 'avr' module) but at the moment each extra function declared in a module takes RAM for code metadata, so you end up using much of your 8kb storing (unused) function metadata!
- coderdude 16y agoI saw your comment in avr.py about saving ram by commenting out the port and ddr methods. Since any Python modules you use are "baked-in" upon compiling, perhaps something could be done to auto-comment functionality in modules that isn't used by the resulting program?
- angusgr 16y agoI actually suggested something similar on the mailing list[1] (static analysis & removal, similar to -ffunction-sections & -gc-sections in gcc.) That's when Dean pointed out his plans to not have the code objects resident in RAM, which he thinks should make that step redundant. [1] http://groups.google.com/group/python-on-a-chip/browse_thread/thread/4eb730def11bca72/afb8d2591a893d81 http://groups.google.com/group/python-on-a-chip/browse_threa...?