Forces only applied during callback

[tshannon]

I'm probably prematurely optimizing, but I'm a little concerned about the fact that forces seem to only be applied during callback.

I'm working on bindings for the Go language, and right currently there is some considerable overhead for c callbacks in Go code.

Is there any such concept as default force like gravity constantly applied internally in the newton loop?

I haven't done any benching yet to see how much of a problem it'll be, but I'm wondering if I'll have to write some C wrapper code to handle this callback entirely in C so I never have to make the translation to Go. Or maybe handle the callbacks in batch or something.

[Julio Jerez]

No Newton does not has a default force.

A call back is function call, also virtual functions are call backs.
The overheaded a callback is or the order 1 to a 10 million time to one the cost of the inner loop of a calculation contact and internal reaction forces.

I has writen bindeing pluging for intepreted languages for newton, and even there cost of calling force and touque is neglegible, including languages like Phyton

[tshannon]

Alright. As I said, I may be prematurely optimizing something that's not an issue.

Thanks,

[Julio Jerez]

In Newton all calbacks are dispached in bach and mode from mutiple threads. They are all re-entrant.

if you assign the same callback to most bodies, the the cost is neglegible because of all of the Branch prediction in maximized
and code cache misses is minimized.
Believe me this is not a problem even on languages like Objective C or Visual basic or even Lua and Phyton, I do not think ti si a proble with GO