valueCount(nil) should be valueCount(0)

[warpling]

The following line (53 in POPPropertyAnimationInternal.h) causes an error

 _POPPropertyAnimationState(id __unsafe_unretained anim) : _POPAnimationState(anim),
 ...
 valueCount(nil),
 ...

I believe the fix is as simple as changing it to valueCount(0), but maybe I'm overlooking something.

[warpling]

Full error: /Users/ryanmcleod/Code/pop-playground-master/Pods/pop/pop/POPPropertyAnimationInternal.h:53:3: Cannot initialize a member subobject of type 'NSUInteger' (aka 'unsigned long') with an rvalue of type 'nullptr_t'

[nickbewley]

I got the same error. Anyone have an idea?

[warpling]

Replacing it with '0' seems to be okay.

On Wed, Mar 4, 2015 at 11:55 AM, Nick Bewley [email protected]
wrote:

I got the same error. Anyone have an idea?

Reply to this email directly or view it on GitHub:
#5 (comment)

[natemcguire]

Same error here, replacing with 0 seems to work

[Francescu]

Could someone PR?

Thanks

[warpling]

It appears this got fixed in Pop awhile back, that said I just cloned this repo fresh and was able to build without issue? If you're still having it though, perhaps you could pod update and pod install?

[Francescu]

Ok I updated the podlock

—
Sent from Mailbox

On Mon, May 18, 2015 at 5:02 PM, Ryan McLeod [email protected]
wrote:

It appears this got fixed in Pop awhile back, that said I just cloned this repo fresh and was able to build without issue? If you're still having it though, perhaps you could pod update and pod install?

Reply to this email directly or view it on GitHub:
#5 (comment)

[warpling]

👍

On Mon, May 18, 2015 at 3:21 PM, Francescu Santoni
[email protected] wrote:

Ok I updated the podlock
—
Sent from Mailbox
On Mon, May 18, 2015 at 5:02 PM, Ryan McLeod [email protected]
wrote:

It appears this got fixed in Pop awhile back, that said I just cloned this repo fresh and was able to build without issue? If you're still having it though, perhaps you could pod update and pod install?

Reply to this email directly or view it on GitHub:

#5 (comment)

Reply to this email directly or view it on GitHub:
#5 (comment)