[ros-kernel] [PATCH] Callbacks

[KJK::Hyperion]

At 00.25 24/05/2004, you wrote:
>But of course I needed to consult WINDBG and a dissembler to see what the 
>specific contents of the callback object structure are,

you needed? I doubt it. Callback objects can safely be opaque. They aren't 
low-level objects like KTHREAD or KPCR containing a lot of useful 
information that can't be retrieved in any other way than by direct access. 
Reversing has to be justified by a real need - this one was a bit gratuitous

I'll give you an example: I was offered a 100% reversed implementation of 
fibers, but I didn't use it. I mean, it didn't even make sense: using a 
whole CONTEXT structure to save 5 or 6 registers? once I understood what 
fibers are for (not very easy to understand from the documentation, given 
the lack of practical examples), I simply rewrote it without even looking 
at the code I had been sent. Binary compatibility sometimes is a non-issue