Tables are nice to take care of a variety of issues. I have yet to see a thermistor that actually follows the "official" curve out to the sort of precision some people seem to expect. That said, storing beta / beta temps and nominal resistance / nominal temp would be a *lot* more flexible than the tables. There's a narrow range in which we actually care about accuracy. Fit the numbers so they work over that range. Outside that range, let it do what ever it does. You could store the real value of the pull up resistor as well.
This would be a break from the past, but the past is gone once you dump 10 bits. If you get a 16 bit ADC tomorrow, it will work with that. If I was doing that, I'd pre-calculate a few often used values at boot (min and max temps for sure). That way you are not hitting the calc routine all the time for the same diata. I'm not sure if a simple table near the control loop set point would be worth it or not. As you pointed out above, just because you can does not mean you should.
This would be a break from the past, but the past is gone once you dump 10 bits. If you get a 16 bit ADC tomorrow, it will work with that. If I was doing that, I'd pre-calculate a few often used values at boot (min and max temps for sure). That way you are not hitting the calc routine all the time for the same diata. I'm not sure if a simple table near the control loop set point would be worth it or not. As you pointed out above, just because you can does not mean you should.