Xan: Created page with "{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}} NOTOC void aw_term (void) ==Description== Terminates use of the SDK. ==Callback== None (returns immediately) ==Notes== This method deallocates any resources used by instances that have been created. Instances are created using aw_create, aw_create_resolved and aw_server_admin. If a call is placed to this method from within a callback or event handler then it cou..."

2025-04-07T19:25:14Z

Created page with "{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}} __NOTOC__ void aw_term (void) ==Description== Terminates use of the SDK. ==Callback== None (returns immediately) ==Notes== This method deallocates any resources used by instances that have been created. Instances are created using aw_create, aw_create_resolved and aw_server_admin. If a call is placed to this method from within a callback or event handler then it cou..."

New page

{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}}

__NOTOC__

void aw_term (void)

==Description==
Terminates use of the SDK.

==Callback==
None (returns immediately)

==Notes==
This method deallocates any resources used by [[SDK_Multiple_Instances|instances]] that have been created. Instances are created using [[aw_create]], [[aw_create_resolved]] and [[aw_server_admin]]. If a call is placed to this method from within a callback or event handler then it could leave dangling pointers in the SDK. Possibly causing a general protection fault (GPF) when it tries to access memory that has been freed.

Any installed callback or event handlers will remain and be used again if the SDK is initialized.

The [[aw_destroy]] method should be used to safely destroy [[SDK_Multiple_Instances|instances]] from within callback or event handlers. This is because [[aw_destroy]] does not deallocate them at once. They merely get flagged as "destroyed" which stops the SDK from processing packets for them.

Calling [[aw_destroy]] for all instances followed by [[aw_wait]] (0) is almost the same as calling aw_term. This is because [[aw_wait]] will deallocate instances marked as "destroyed". Only difference is that it would not be necessary to call [[aw_init]] again before creating instances.

Note that [[aw_destroy]] followed by [[aw_wait]] (0) within a callback or event handler is as bad as aw_term because both would deallocate the instance.

==Arguments==
None

==Argument attributes==
None

==Return values==
None

==Returned attributes==
None

==Usage==
#include "Aw.h"
#include "[[Reason.h]]"

int main (int argc, char *argv[])
{
if ([[aw_init]] (AW_BUILD) != [[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]])
{
printf ("Build #%d of Aw.dll is required to run this bot.\n", AW_BUILD);
return 1;
}

/* ... */

[[aw_term]] ();
return 0;
}

==See also==
*[[SDK_Application_Structure|Application structure]]
*[[aw_init]]
*[[aw_init_bind]]
*[[aw_create]]
*[[aw_create_resolved]]
*[[aw_server_admin]]

[[Category: SDK Methods|T]]

Aw term - Revision history