cpBody function no const cpBody *

[pat]

[slembcke]

Just inconsistencies I guess. I don't often think to add const. I did with the vector operator functions because I wanted to ensure that they got optimized well. Is there any particular reason you are defining them as const to begin with?

In general things like shapes and bodies are not constant. Tagging getter functions maybe makes sense, but you can't do much with a read only shape or body.

[pat]

yea i figured optimization could be a reason for it, though i'm not sure that it would make a difference since its pointers, with the cpBodyL2W/W2L functions those cpv calls take const cpVect's (which i wouldnt think would matter in the long run since its still doing a copy).

Like i'm working on a world editor and stuff like plotting shapes i ushaully keep the body constant incase the project gets more of a team and people think they should be playing with other stuff besides whats not constant (which is really th only reason for const i'd say).

The other times when i'll use const is so that the person writing code with my code knows that that value that there sending is not going to be modified, Which i think would be a good thing in chipmunk to do for people who are new to game programming and don't know what is actually gonna be modifying stuff and not. Its pretty standard to do this with c++, i'd imagine the same with c but i don't really have the background to say that.

[slembcke]

Well, I added const to static inline functions and macro templated functions in the headers. I think that should cover most of the cases that you were talking about. I'll have to make a deeper inspection later if I want to get all of them.

[pat]

Sweet, thats great. I think that should cover most everything

[BLWNKL]

Hi all...
In trying to learn how to use cpBodyLocal2World, I discovered that the object (sprite) I wish to use as the "target" of a projectile actually has no cpBody (since it's not included in the space because I don't want it to actually participate in collisions per se). A good way to think of this is as "an aiming point" in the space.
So I'm wondering if (based on the discussions in this thread about const cpBody objects) this approach makes sense? Or is there a better way to accomplish what I describe?
BTW, I'm struggling with the notion of "world coordinates". Are they different from the iPhone view coordinate system, where 0,0 is upper left?
Thanks in advance for any thoughts you may share.

[ShiftZ]

BLWNKL
There is no such things as iPhone coordinate system, and cpBodyLocal2World doesnt concerned with screen coords. You have to have somekind of Viewport object, whitch can translate from screen coordinates to world coordinates and back taking in a count camera position, gl projection matrix ect.