From 0f7d5bf366aa730e6247a0452f264510cb6d9ed9 Mon Sep 17 00:00:00 2001 From: Patrick Pelissier Date: Sat, 15 Jun 2024 09:51:51 +0200 Subject: [PATCH] Update doc --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3ae907c2..82f14e15 100644 --- a/README.md +++ b/README.md @@ -6955,11 +6955,14 @@ M_LET( (b, a), string_t){ string_fputs(stdout, b); } > [!NOTE] > The user code shall not perform a return or a goto (or `longjmp`) within the next block -> with a terget outside this block or a call to an exit function. -> Otherwise the clear code of the object won't be called. +> with a target outside this block. +> Otherwise the clear code of the object isn't called. > However, you can use the break instruction to quit the block > (the clear function will be executed) or throw an exception. +If a call to an exit function in the next block is performed, +the clear code of the object isn't called. + You can chain the `M_LET` macro to create several different variables. ##### `M_LET_IF(init_code, test_code, clear_code [, else_code] )`