Andrey Volodin

Just faced same thing. Have you ever found a solution for that?

I think this error appears only with ObjCpp compilers.. I have to look at it more precisely a bit later. I actually use ObjC++ now in my project with 3.5...

I think you should open this issue in cocos2d classic

I honestly don't really understand why color and colorRGBA are separated. Maybe for cascading purposes, I didn't look into that yet. Will see what we can do about it.

I also don't understand why we still maintain types like `ccColor4F`. The whole color things must be refactored I guess.

Making it a struct would be much better, but Obj-C doesn't have methods for structs as Swift has :(

X-men (cocos2d-x) are now responsible for all maintenance of web-site and forum. I will try to contact them, but please also try to raise a topic on their forum as...

I got rid of CCTouch tottally in 3.5. Since we don't have Android anymore, we can use UITouch directly. Now CCTouch is just a define for legacy versions. `#define CCTouch...

Implemented in separate branch for now, will be merged into 3.5+.

I just saw this pattern in SwiftPM docs: ``` let package = Package( name: "Paper", products: [ .executable(name: "tool", targets: ["tool"]), .library(name: "Paper", targets: ["Paper"]), .library(name: "PaperStatic", type: .static, targets:...