[Tutorial] Guidelines, conventions, and assumptions about the AMX API intended for consumers and extenders - Printable Version

+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Plugin Development (https://sampforum.blast.hk/forumdisplay.php?fid=18)
+--- Thread: [Tutorial] Guidelines, conventions, and assumptions about the AMX API intended for consumers and extenders (/showthread.php?tid=659106)

---

Guidelines, conventions, and assumptions about the AMX API intended for consumers and extenders - IllidanS4 - 23.09.2018

Since there are a rising number of plugins that hook the AMX API functions, I have decided to make a guide for plugin creators to ensure these plugins are compatible and can cooperate with each other and with any other compliant plugin.

Guidelines, conventions, and assumptions about the AMX API intended for consumers and extenders.

These guidelines are useful not only to people who hook the AMX API, but also to any plugin creator that uses the AMX API. They specify how to write code that can interact with different languages and conventions and is generally compatible with any AMX extension.

---

Re: Guidelines, conventions, and assumptions about the AMX API intended for consumers and extenders - VVWVV - 23.09.2018

Good job!

---

Re: Guidelines, conventions, and assumptions about the AMX API intended for consumers and extenders - IllidanS4 - 26.09.2018

The guidelines were moved to a new repository, together with new proposals about name mangling and calling conventions.

---