The word "hooking" usually means that you're doing something that you're not supposed to do, there's no hooking in terms of writing your own native functions.
Quote:
Originally Posted by x6herbius
I could call that command from the second plugin and the code from the first would be run, correct?
|
Yes.
Quote:
Originally Posted by x6herbius
In the case of forwards, the prototype would be defined in the first plugin
|
When you write a plugin that will expose it to others, you provide a separate include file that contains prototypes for all natives and forwards. See SM includes for a good examples.
Quote:
Originally Posted by x6herbius
and, whenever it was called, the code from the second plugin would be run instead?
|
Yes.
Quote:
Originally Posted by x6herbius
If that's along the right lines then I think I get it. If more than one plugin used a forward from a parent plugin, though, which would be run first?
|
You should not rely on the order of execution. When the forward is called, it's assumed that all plugins have the same rights. Don't know the exact implementation though.
__________________