| |||||||||||||
Object-oriented design patterns in the kernel, part 1Object-oriented design patterns in the kernel, part 1Posted Jun 6, 2011 15:00 UTC (Mon) by michaeljt (subscriber, #39183)In reply to: Object-oriented design patterns in the kernel, part 1 by Cyberax Parent article: Object-oriented design patterns in the kernel, part 1
>> In C you can get round that with the following (you don't have to like it if you don't want to!)
>> void somefunction_wrapper() { >> somefunction_core(); >> important_cleanup_code(); >> } > > That's even worse. You'll have either put resources into global variables > (yikes!) or pass around some kind of 'local frame' structure. Essentially > reinventing exceptions.
Not quite sure what you mean there.
[...]
>> And if you are going to think about it beforehand anyway you can also return a pointer to an error structure (which can potentially be statically or dynamically allocated) in C rather than just an integer error code. (That was just an example of course as there are lots of other ways to achieve the same thing.)
Not really - you just return a pointer where C traditionally returns an integer error code, and pass that on if a function you call returns a non-NULL error pointer.
(Log in to post comments)
|
|||||||||||||