[Pawn] y_hooks v4(ish)

[JustMichael]

I'm a fan of both 2,3 and 4. Since they don't over complicate anything and looking at the rest it doesn't look like newbies will comprehend that and will most likely push them away.

Good.

I don't mind `continue` or `next` as keywords to move to the next hook maybe even `next` and `cancel` or `continue` and `break` (depends if you want to mix in with the current keywords)

Though thinking about it `continue` and `break` are keywords that exist in many languages, and I don't know how I feel about re-using them for a different cause, it might confuse people.



`next` and `cancel` seem like good alternatives, if you have no objections to them. They are easy to comprehend and they are not used elsewhere.

The major problem with new keywords is compatibility - making sure they don't break existing code which ma already use them as function or variable names.

I'm not a big fan of putting `hook` in front of every keyword that doesn't feel right to me at all.

Do you mean you don't like the `hook public` and `hook native` syntax as well? ?There isn't really another way to do that.

I am okay with `hook public` and `hook native` but not okay with `return hook continue(a 5);` or something like that. It might just be me being used to the previous way.