5 ms·
Nope. Undefined behavior on obviously incorrect input isn't a bug in my world. ( might be in other circumstances )
by kuboble 4y ago
Nope.
Undefined behavior on obviously incorrect input isn't a bug in my world. ( might be in other circumstances )
- taftster 4y agoYou must be a C programmer.
- insightcheck 4y agoHaha. I was thinking along similar lines as kuboble, but then I'm someone in the process of trying to learn C. I agree, upon further thought, that at least an error message would be better for the user (e.g. "Maximum timer duration exceeded").
- dogecoinbase 4y ago"Undefined behavior consists of exactly one proposition, to wit: There must be compiler engineers whom the language standard protects but does not bind, alongside developers whom the language standard binds but does not protect." (source: https://twitter.com/jckarter/status/1558181259314167808 https://twitter.com/jckarter/status/1558181259314167808 )
- diarrhea 4y agoI mean, the query is “timer $period”. It’s correct in its syntax, a period’s a period. It’s not asking for “timer TIMMY; DROP TABLES”. That’s incorrect input.
- nomel 4y agoIt's not incorrect input. It's incorrect handling of accepted input.
- JohnFen 4y agoUndefined behavior on obviously incorrect input is always a bug. Incorrect input should give you an error.