Re:Why Is SQLite Coded in C? (2017)
by falcolas on Thursday March 15, 2018 @09:39AM
(#16592705)
Honestly, to help avoid mistakes, I would keep it as a function call. Sure, it adds to the stack depth, but it also ensures a separate return doesn't cause the lock to be lost.
There's also the goto pattern, but anytime you separate a lock from an unlock by more than a screen's worth of text, they're forgotten.
Re:Why Is SQLite Coded in C? (2017)
by aidenn0 on Thursday March 15, 2018 @01:40PM
(#16594919)
And inline functions don't even add stack depth. It's still something that happens manually though. Every item that needs to be done manually and doesn't cause obvious failures when not done adds to development costs.
There's also the goto pattern, but anytime you separate a lock from an unlock by more than a screen's worth of text, they're forgotten.