Token Categories

[ghost]

Here are the categories for block values that we decided on today. Each block could fall under 1 of each category, and any token on the block can be chosen with the potentiometer. Please review and make sure these categories make sense.

• Values
  • 0
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • .
  • X
  • Y
  • Z
  • Sum
  • Count
• Assignments & Operators
  • +
  • -
  • /
  • *
  • ^
  • %
  • =
  • !=
  • <

  • =

  • <=
  • !
• Control
  • while
  • endwhile
  • if
  • else
  • endif
  • (
  • )
• Statements
  • OUT1
  • OUT2
  • OUT3
  • OUT4
  • OUT5
  • Print

[gstro]

To expand on Tyler's notes, we're creating 4 subsets (wheels) of the total grammar with 16 (maximum) selectable functions each to ensure reliable ADC reads (4-bit precision). These wheels will likely be color-coded to help students conceptualize their different utility in the programming structure.

:+1: Categories look good to me, @htylo!

[jmickiewicz]

I would include an explicit assignment operator. Even though it will code to white space by itself There is space in the assignment & operators category where it would belong. This would in my mind make it clearer to read "x2+1" vs "x:2+1"

[gstro]

A little more clarification:

• In Values:
  • the . is a decimal to permit floating point values
  • X, Y, Z, Sum, and Count are variables
• In Assignments and Operators:
  • ^ is raising to the power
  • = is the token for the == comparison, and will show as == on the wheel display
• In Control:
  • the ( and ) parentheses help with order of operations, not as requirements for control parameters (e.g. our grammar is if x > 5 _not_ if ( x > 5 ) )
• In Statements:
  • OUTn will map to the outputs defined in #84 (LCD, Speaker, LED, Servo, etc).
  • Print may output to LCD, BBB, or both.