In Mathematics, especially Real Analysis and Topology, the use of open and closed intervals is endemic. The open interval \\((a,b)\\) is the interval \\(a < x < b\\) while the closed interval \\([a,b]\\) includes the endpoints: \\(a \\le x \\le b\\). There is also the notion of a closed\/open interval \\([a,b)\\): \\(a \\le x < b\\).<\/p>\n
You\u2019ve probably noticed that operators in most programming languages operate on closed\/open intervals. A common example is the sub string operator, Fernando Hurtado Cardenas has a post that explains this seeming anomaly<\/a>. Although using a closed interval seems more logical and has a nice symmetry, it often leads to unexpected edge cases and brittle code with a lot of special cases. The worst thing is that the closed interval works most of the time. It\u2019s those easy to overlook corner cases that trip you up. Cardenas discusses some of those edge cases and offers a pretty good argument that the annoying closed\/open interval is the right thing. Take a look at his post. If nothing else, you\u2019ll feel better about those operators using closed\/open intervals.<\/p>\n","protected":false},"excerpt":{"rendered":" In Mathematics, especially Real Analysis and Topology, the use of open and closed intervals is endemic. The open interval \\((a,b)\\) is the interval \\(a < x < b\\) while the closed interval \\([a,b]\\) includes the endpoints: \\(a \\le x \\le … Continue reading substr<\/code> say, found in many languages. They all work pretty much the same. The function substr(a,b)<\/code> specifies the string of bytes starting at byte \\(a\\) up to but not including byte \\(b\\). If you\u2019re like me, you\u2019ve probably occasionally found this annoying. If you want bytes 2, 3, and 4, it seems natural to write substr(2,4)<\/code> rather than substr(2,5)<\/code>.<\/p>\n