SPI example has non-sensical inclusion of math expression that's actually longer than the number it represents about t2-docs HOT 5 CLOSED

Representing large numbers like 4,000,000 as 4*1000*1000 instead of 4000000 makes them easier to read, debug, and maintain.

I'd keep the clockspeed as it is, but I agree more readable property names for polarity and phase would be an improvement.

from t2-docs.

If we were using Java/Python/Rust, representing it as 4_000_000 would be ideal. ;) Since this is for docs, it probably if we show the audience clock speed can just be represented as 4000000. (Persons writing their own codebases can use the expanded *1000 forms. Different audience.)

+1 to polarity and phase. Where did terms CPHA and CPOL even come from? We probably sourced them from Arduino examples way back in the day, but I haven't really seen them used outside of that domain. (Also see "mode" etc.)

I feel like "clockSpeed" is more applicable than "frequency" but YMMV.

from t2-docs.

Hi guys, I'm new here, and am a pretty green programmer. Would it make sense to create a constant titled MHz (or some other descriptive name) instead, and set it equal to 1000x1000? That way the expression could become "4*MHz" which could be even more readable.

from t2-docs.

Hi @Frijol ! Can the issue be closed now that the pull request has been merged? Or is there something else that needs to be done?

from t2-docs.

Yes, thanks for noticing!

from t2-docs.