Robot Wrapper about pinocchio HOT 7 CLOSED

• Not throwing exceptions would be great.
• Not making explicit dynamic allocations (using new operator) would be great.

If this conflicts with your development roadmap, then no worries.

from pinocchio.

Concerning the exceptions, why this precise request?

from pinocchio.

Our whole code base is supposed to be exception-free. I know this is not currently the case in pinocchio, which is why this is not a hard requirement.

from pinocchio.

Ok. If you want you can just use the instruction -fno-exceptions with gcc.
I think for lambda user, exceptions are mandatory that why we try to populate our code with them.

from pinocchio.

Noted, thanks.

from pinocchio.

It indeed is: please no throw in construction and destruction (just
image what can of torture you are generating on the poor stack when
creating memory with a destruction phase to throw something).

On 02/22/2016 04:44 PM, Antonio El Khoury wrote:

Our whole code base is supposed to be exception-free. I know this is
not currently the case in pinocchio, which is why this is not a hard
requirement.

—
Reply to this email directly or view it on GitHub
#108 (comment).

from pinocchio.

A robot wrapper have been implemented in https://github.com/stack-of-tasks/tsid

from pinocchio.