3 ms·
Oops! Completely missed that we were talking about C. I'll continue under the assumption that C is capable of equally powerful compile-time asserts. > it eff
by MaxBarraclough 8y ago
Oops! Completely missed that we were talking about C.
I'll continue under the assumption that C is capable of equally powerful compile-time asserts.
> it effectively defines lots of distinct subtly different pseudo-platforms, each a set of assumptions
Indeed, but using this approach, all that's needed to define a new 'ordinary platform C' is a clearly defined set of requirements. No need for a whole new standard in the usual sense.
> experts to provide a blessed set of assumptions
Sure, and that's compatible with this approach. It could take the form of a header file.
- int_19h 8y agoI'm perfectly fine with the idea of code-as-specification like that. And you're right, a lot of these assumptions could probably be so encoded (some I'm not sure about - e.g. how would you static_assert for two's complement, without triggering UB?). But I think this sort of thing would need some official blessing to be widely adopted, regardless of whether it's a written spec or a header.
- MaxBarraclough 8y ago> how would you static_assert for two's complement, without triggering UB? Good question, I'm not certain that's possible. A quick google turned up surprisingly little. The ghastly hack alternative would be to detect which compiler/target we're dealing with and compare against a whitelist. > I think this sort of thing would need some official blessing to be widely adopted, regardless of whether it's a written spec or a header. It would certainly help to have it properly branded and given real credibility, yes. I'm reminded of MISRA C, which has a good deal of tooling and documentation.