Talk:Petit Computer 3/@comment-14600979-20140709193418/@comment-9531161-20140710065320

In my opinion, they have two options that would work well:
 * Have lower types brought up to higher types in math expressions (like you described).
 * Do not allow types to be mixed, but variables can be interpreted as different types by the inclusion or removal of %.

The first solution is how most conventional programming languages do it, so I don't see why they wouldn't do it too. This would also lend itself well if the variable types are actually treated separately.

However, if these variables are not treated separately, the second solution would seem appropriate. The wording of "Handling of integer such as real will sign additional type of old-fashioned such as (%)" gets me worried, because it sounds like integers can be "handled" like a real when you use %, and % will simply access extra (or perhaps not?) bits in the integer in the "old-fashioned" way, which was fixed point. What I basically mean is that all numbers will still be fixed point, but will be interpreted as an integer by default (with the decimal ignored) when % is omitted, but the decimal bits will be taken into account when % is used. This could still allow for some optimizations for integer math, since on PTC's end it's as easy as shifting the bits to the right a certain amount and then treating the value as a real integer. This is still much faster than performing "custom" operations on fixed point types all the time, but it would still suck considering the 3DS has an FPU. If Smileboom takes this route, it would be out of sheer laziness. Boooooo.