The code in .pk3 files are quake bytecode. The trap_* functions wrap the work needed to transfer data across the VM/native boundary. On Jan 26, 2011 5:30 AM, "Ben Noordhuis" <i...@bnoordhuis.nl> wrote: > On Wed, Jan 26, 2011 at 11:03, Yasir I. Al-Dosary - zgzg2020™ > <yasiraldos...@yahoo.com> wrote: >> Hello to all active and lurkers out there who may have an answer, >> Does anyone know what trap_ is used for? For example: >> trap_BotTouchingGoal() >> trap_BotChooseNBGItem() >> ...etc >> Why not BotChooseNBGItem() directly? > > The trap_* functions are the glue that connects the SDK with the > engine. It allowed iD to release the SDK without opening up the engine > (back in 2000 or so). > >> Furthermore, I would like to skip those trap_ and go directly to the function, >> is that alright??? > > You could if you linked engine and SDK into one big binary but why would you? > _______________________________________________ > ioquake3 mailing list > ioquake3@lists.ioquake.org > http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org > By sending this message I agree to love ioquake3 and libsdl.
_______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
