You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, any SPICE exception causes rb_raise() from within C to signal the error. This isn't a very good practice due to the call bypassing any memory cleanup code subsequent to the rb_raise() statement, as pointed out by Will Levine here.
SpiceRub uses NMatrix very frequently to represent Cartesian vectors and state/position arrays, so this could be a potential cause of memory problems in the future. I would like to switch to an error code system where the C function returns an error code which is parsed in Ruby as suggested in the above thread. There might possibly be a better way to this.
The text was updated successfully, but these errors were encountered:
As of now, any SPICE exception causes rb_raise() from within C to signal the error. This isn't a very good practice due to the call bypassing any memory cleanup code subsequent to the rb_raise() statement, as pointed out by Will Levine here.
SpiceRub uses NMatrix very frequently to represent Cartesian vectors and state/position arrays, so this could be a potential cause of memory problems in the future. I would like to switch to an error code system where the C function returns an error code which is parsed in Ruby as suggested in the above thread. There might possibly be a better way to this.
The text was updated successfully, but these errors were encountered: