Re: OT: This Swift thing

References	(1 earlier) <CANc-5UyPyvGJRizcz2f7N=KPvo3TH6LcWGxeSWHbgOm1XvYUuA@mail.gmail.com> <CAAu18hd8Spu98vcx6M+JQqZiYXXXu38et1i2quSNy506i=ESYA@mail.gmail.com> <1685918893423520358.034637sturla.molden-gmail.com@news.gmane.org> <CAPTjJmpRAL2HHtdQ410AgSU44mhaXy3H6XTYbRjnc_Cc4eZv6g@mail.gmail.com> <538E7ABE.4060200@gmail.com>
Date	2014-06-04 12:21 +1000
Subject	Re: OT: This Swift thing
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.10667.1401848481.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Wed, Jun 4, 2014 at 11:47 AM, Michael Torrie <torriem@gmail.com> wrote:
> A Swift string is simply a one-to-one mapping of the NSString class.
> Apple claims it is "unicode compliant" whatever that means.
>
> https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/StringsAndCharacters.html

Yeah, I was looking at the same page. Note how, further down, a syntax
is given for non-BMP character entities (the same as Python's), and
then a bit more down the page, iteration over a string is defined,
with a non-BMP character in the example string. That's a good start.
However, keep going down... and you find that the length of a string
is calculated by iteration, which is a bad sign. I don't see anything
about indexing, which is the most important part.

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: OT: This Swift thing Chris Angelico <rosuav@gmail.com> - 2014-06-04 12:21 +1000

csiph-web