David Johnson-Davies
David Johnson-Davies
> Also, one other thing that I think might make uLisp more accessible to the wider Arduino community is making uLisp a file/library to be included, not its own sketch....
> I implemented unlimited extensions (using malloc) on my fork and I don't see any performance issues. The performance hit comes from **getminmax()**, which has to do table lookups at...
> The problem wit this is that it hard-codes 2 tables -- if you pass a builtin that would appear in table 3, it would look and say OK, name...
Interesting ideas. > Instead of just using a type enum and using special low values as the car pointer you could statically allocate structs for the types and point to...
Thanks! I'll have a look.
Yes, good point, thanks.
You've done a great job with these diagrams, considering the complexity of the parts. The only thing I can't find is the Arduino pin numbers; or was that a conscious...
@pcfreak1201 I know I can use those, but what I'm referring to are the numbers labelled "ARDUINO PIN" on the other pinout images such as: https://github.com/SpenceKonde/DxCore/blob/master/megaavr/extras/DA28.md
It's just that anyone coming to DxCore from the standard Arduino range will be used to using them. For example: https://www.arduino.cc/reference/en/language/functions/digital-io/digitalwrite/ At least add a note to that effect on...
@ObviousInRetrospect > Arduino PIN numbers are inscrutable, create extremely non-portable code, and really should not be used directly. Whether or not you prefer using pin names like **PIN_PD6** to Arduino...