Swifter – A Twitter Framework written in Swift

Re:Swifter – A Twitter Framework written in Swift by mikevm on Saturday June 14, 2014 @01:47PM (#7893214)

Why is the code so verbose?

     let result = CFURLCreateStringByAddingPercentEscapes(kCFAllocatorDefault, self.bridgeToObjectiveC(), charactersToLeaveUnescaped, charactersToBeEscaped, CFStringConvertNSStringEncodingToEncoding(encoding)) as String

[ Parent | on HN ]

Re:Swifter – A Twitter Framework written in Swift by mattdonnelly on Saturday June 14, 2014 @01:55PM (#7893224)

Almost all of Apple's frameworks written in Objective-C and C are incredibly verbose. It's just an adopted style of the language and although it's often a little difficult to look at, it can be quite helpful sometimes

[ Parent | on HN ]

Re:Swifter – A Twitter Framework written in Swift by menzoic on Saturday June 14, 2014 @01:56PM (#7893227)

Swift should be less verbose

[ Parent | on HN ]

Re:Swifter – A Twitter Framework written in Swift by mattdonnelly on Saturday June 14, 2014 @02:00PM (#7893240)

It is actually, but functions like the one mentioned above are bindings for Objective-C / C functions and share the same name as the function they bind to

[ Parent | on HN ]

Re:Swifter – A Twitter Framework written in Swift by cschep on Saturday June 14, 2014 @01:56PM (#7893229)

While Swift is a new language, that method is calling into very old framework code written in Objective-C. Which is very verbose.

[ Parent | on HN ]

Re:Swifter – A Twitter Framework written in Swift by Glide on Saturday June 14, 2014 @02:33PM (#7893315)

That looks more like a C function call. If it was an Objective C message the named parameters would make it far more verbose (and readable).

[ Parent | on HN ]