• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Data, enumerateBytes: separate blocks?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Data, enumerateBytes: separate blocks?


  • Subject: Re: Data, enumerateBytes: separate blocks?
  • From: Charles Srstka <email@hidden>
  • Date: Mon, 25 Dec 2017 12:44:17 -0600

> On Dec 25, 2017, at 12:23 PM, Daryle Walker <email@hidden> wrote:
>
> Not quite.
>
> My first versions of this idea, pre-Swift and therefore using NSData with
> Objective-C, did use the direct search functions that come with the NSData
> API. There seems to be a detail you missed in my sample code that explains
> the use of “enumerateBytes”:
>
> LF-only is also a searched-for separator.
>
> That means no matter what, I must find the first CR and the first LF. Then I
> compare their relative positions (and check for another CR if the spacing is
> right). What happens if whichever byte value is second is gigabytes away from
> the first? (Or equivalently, only one value is present and there’s gigabytes
> of trailing data to fail to find the other value.) I would end up wasting the
> user’s time for a second result I’d never use.

With either Collection<UInt8> or Data, the value that index(of:) returns for
the second value will be one greater than what it returns for the first value
in that case, regardless of how the data is stored under the hood.

Charles

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Data, enumerateBytes: separate blocks? (From: Daryle Walker <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Quincey Morris <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Daryle Walker <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Quincey Morris <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Daryle Walker <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Quincey Morris <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Daryle Walker <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Charles Srstka <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Quincey Morris <email@hidden>)
 >Re: Data, enumerateBytes: separate blocks? (From: Daryle Walker <email@hidden>)

  • Prev by Date: Re: Data, enumerateBytes: separate blocks?
  • Next by Date: Re: Data, enumerateBytes: separate blocks?
  • Previous by thread: Re: Data, enumerateBytes: separate blocks?
  • Next by thread: Re: Data, enumerateBytes: separate blocks?
  • Index(es):
    • Date
    • Thread