News for hackers. Stuff that matters.

A comment on A Cross-Platform String Library Written in Swift. Parent comment

Re:A Cross-Platform String Library Written in Swift by TazeTSchnitzel on Sunday March 05, 2017 @01:53PM (#13797740)
> 1) Function names are misleading or not descriptive enough. E.g. isAlpha(). I assumed this meant is alphanumeric, but it actually means isAlphabetic

Why should it mean alphanumeric? C's isalpha() also tests for being a letter, for instance, and has isalnum() for alphanumericness.

> If it's not uppercased of course its lowercased

If you're working exclusively with ASCII and ignoring non-letter characters, yes. But is this library bound by those constraints?

[ Parent | on HN ]
Re:A Cross-Platform String Library Written in Swift by setr on Sunday March 05, 2017 @05:23PM (#13799172)
what non-letter character should succeed in both isLowercase and isUppercase?
[ Parent | on HN ]
Re:A Cross-Platform String Library Written in Swift by TazeTSchnitzel on Monday March 06, 2017 @04:17AM (#13801577)
None. But letters can be neither lowercase nor uppercase.
[ Parent | on HN ]
Re:A Cross-Platform String Library Written in Swift by setr on Monday March 20, 2017 @02:21AM (#13912159)
In which case, the function(s) should really be throwing some kind of error, since they can't reasonably be applied to the input.

But checking !(isUppercase(str) || isLowercase(str)) to see if its not case-able(?) is absurd

Obviously you'd instead want the function notCaseable(str).

[ Parent | on HN ]