diff options
| author | 2026-04-12 13:22:14 -0400 | |
|---|---|---|
| committer | 2026-04-12 13:22:14 -0400 | |
| commit | c633226d2b615f46ef38cc99603775dccdf96ecd (patch) | |
| tree | 645a7cf068eac001031d81734b9649ac1c26b019 /meson.build | |
| parent | 7c83f46445cee77e935720ec8291886eb21248d7 (diff) | |
| download | libalabaster-c633226d2b615f46ef38cc99603775dccdf96ecd.tar.gz libalabaster-c633226d2b615f46ef38cc99603775dccdf96ecd.tar.bz2 libalabaster-c633226d2b615f46ef38cc99603775dccdf96ecd.zip | |
Signed-off-by: Andrew Opalach <andrew@akon.city>
Diffstat (limited to 'meson.build')
| -rw-r--r-- | meson.build | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meson.build b/meson.build index 0dffee3..1563d11 100644 --- a/meson.build +++ b/meson.build @@ -39,7 +39,7 @@ endif # The definition of the assert() macro is determined by the _last_ place where # <assert.h> was included, because it redefines itself each time. Making it # unnecessarily complicated to predict if assert() will be active or a no-op. -# Maybe I just haven't seen why this could make sense but to me it's counterintuitive. +# Maybe I just haven't seen why this could make sense, but to me it's counterintuitive. # We define al_assert() to be unchanging and let any dependencies figure it out for themselves. # Another note, which I hadn't heard before but, this clearly makes relying on NDEBUG # for anything other than asserts a very bad practice. |