> On 16 Jul 2016, at 22:16, Andrew Trick wrote:
>
> I don’t know what the recommended idiom is or if the syntax has changed from
> Swift 2 to 3, but I would do something like this:
>
> withExtendedLifetime(data) {
> let dataStart = UnsafePointer(data.bytes)
> myProcessdata1(dataStart,data.le
On Sat, Jul 16, 2016 at 1:16 PM, Andrew Trick via swift-users
wrote:
>
>> On Jul 16, 2016, at 5:28 AM, J.E. Schotsman via swift-users
>> wrote:
>>
>> A mysterious bug has got me thinking about using UnsafePointer with
>> NSData (Swift 2).
>>
>> Is this safe:
>>
>> let data:NSData = …
>> let dat
> On Jul 16, 2016, at 5:28 AM, J.E. Schotsman via swift-users
> wrote:
>
> A mysterious bug has got me thinking about using UnsafePointer with
> NSData (Swift 2).
>
> Is this safe:
>
> let data:NSData = …
> let dataStart = UnsafePointer(data:NSDAta.bytes)
>
> myProcessdata1(dataStart,data.l
A mysterious bug has got me thinking about using UnsafePointer with
NSData (Swift 2).
Is this safe:
let data:NSData = …
let dataStart = UnsafePointer(data:NSDAta.bytes)
myProcessdata1(dataStart,data.length)
… (no more references to data)
And this:
let data:NSData = …
myProcessdata2(data)
…
