# Problems with deprecations of islower, lowercase, isupper, uppercase

**URL:** https://discourse.julialang.org/t/problems-with-deprecations-of-islower-lowercase-isupper-uppercase/7797
**Category:** Internals & Design
**Created:** [December 15, 2017, 8:19pm UTC](https://discourse.julialang.org/t/problems-with-deprecations-of-islower-lowercase-isupper-uppercase/7797 "2017-12-15T20:19:32Z")
**Posts on this page:** 1
**Showing post:** 138

<div class="post-metadata">

### Author: ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)
#### Post date: [December 24, 2017, 9:06am UTC](https://discourse.julialang.org/t/problems-with-deprecations-of-islower-lowercase-isupper-uppercase/7797/138 "2017-12-24T09:06:20Z")

</div>

> [@jeff.bezanson](#):
>
> It’s weird for code to contain str[6:9]; usually the 6 is derived by searching for something.

Many record formats are defined with fields of fixed numbers of characters, padded with ’ ’ or 0s.  
Also, for certain types of text analysis, you want to look at the distance in characters between two words or concepts in a sentence (having one type of ‘i’ take 1 byte, and another 3 bytes, totally screws up those sorts of calculations, and it’s not worth the performance hit there to make a little more accurate by looking by first doing decomposition/composition and calculating using grapheme clusters (something I had to be convinced about myself by an expert on computational linguistics, I thought using graphemes would be necessary, but Unicode codepoints are fine).

---

_[View the full topic](https://discourse.julialang.org/t/problems-with-deprecations-of-islower-lowercase-isupper-uppercase/7797)._