, @Roy Eltham
Would any of you (or anyone, really) be amenable to getting one or both of some kind of fixed-point (runtime) decimal/not-necessarily-whole-number support and/or a 64bit int (longlong, dlong, qword, int64?) in openspin or fastspin sometime in the future (preferably in openspin, since it produces compact bytecode output)? I know this may raise some people's hackles, and may be totally out of the question for technical reasons, but I'm running into more and more devices for which writing a driver is painstaking when e.g., sensor values need to be calculated to some absolute scale (Bosch, Melexis, TI devices I find, especially) that either yields small fractional numbers or those far in excess of the Prop's signed 32-bit long. I've used objects like F32 or UMath64 for some things before, but I'm also not talking about a simple var = 0.123 * 2 or var = 2^48 type operation here. Rather, formulas that are already a paragraph or half a page long or more in native form; it becomes too difficult to follow, either for me or for someone trying to read my code, when implemented with one of the former. I absolutely adore SPIN, but this is one thing that makes writing some software so difficult, I find myself shelving it, at least for an extended period of time, to come back to it later and try to "chisel away a little bit more."
Thanks for your consideration even if the answer is no!
WIP Spin/PASM drivers: (P1) (P2)
P1 & P2: LSM9DS1, US2066, MLX90621, SHT3x, SSD1306, TCS347x, MAX31856, nRF24L01+, MLX90614, DS28CM00, TSL2591, INA219, SX1276/LoRa, VEML6075 | P1 only: TMC2130, MAX9744, CC1101, SX1231, LM75, DS18B20, Si7021, BT81x, MB85RC | P2 only: W25Qxxx, INA260 | WIP: L3G4200D, IL3820, MPU9250, MLX90640 | Stalled: SI446x, BMP280, BME680, BNO055