diff options
| author | João Valverde <j@v6e.pt> | 2023-01-12 00:30:50 +0000 |
|---|---|---|
| committer | João Valverde <j@v6e.pt> | 2023-01-12 00:59:15 +0000 |
| commit | 25d4a099f7c5578d1d43f66f8e9ea567f698cc4b (patch) | |
| tree | 6b49238e2fcef75e8cf12f2c32cf0c7deea7e8a9 /doc/README.developer | |
| parent | 640c44f24edef4ee3062d77b5fc8366db64e85c4 (diff) | |
Remove WS_DISABLE_ASSERT
Assertions can be enabled/disabled using WS_DISABLE_DEBUG. The extra
granularity afforded by WS_DISABLE_ASSERT seems unnecessary.
Diffstat (limited to 'doc/README.developer')
| -rw-r--r-- | doc/README.developer | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.developer b/doc/README.developer index d9281c9f8e..317dfbaaca 100644 --- a/doc/README.developer +++ b/doc/README.developer @@ -569,8 +569,8 @@ used for that purpose. Use assertions to catch logic errors in your program. A failed assertion indicates a bug in the code. Use ws_assert() instead of g_assert() to -test a logic condition. Note that ws_assert() will be removed with -WS_DISABLE_ASSERT. Therefore assertions should not have any side-effects, +test a logic condition. Note that ws_assert() can be removed at compile +time. Therefore assertions should not have any side-effects, otherwise the program may behave inconsistently. Use ws_assert_not_reached() instead of g_assert_not_reached() for |