From fbf3fea0c86a6cece7b5a94b40fb6182911823a9 Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Fri, 3 Jul 2026 15:27:27 +0000 Subject: [PATCH] fix(packaging/windows): Inno [Code] comment brace-nesting trap broke ISCC The PublicFwParam doc comment contained a literal code-constant token; Inno's { } comments don't nest, so its closing brace ended the comment early and the trailing text parsed as code ("'BEGIN' expected", compile aborted). Reworded to avoid the literal braces + added a warning note. Verified: the [Code] section has no other nested-brace-in-comment traps. Co-Authored-By: Claude Fable 5 --- packaging/windows/punktfunk-host.iss | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/packaging/windows/punktfunk-host.iss b/packaging/windows/punktfunk-host.iss index 86e9e45..7205578 100644 --- a/packaging/windows/punktfunk-host.iss +++ b/packaging/windows/punktfunk-host.iss @@ -298,7 +298,9 @@ end; { Firewall scope: the "allowpublicfw" task opens the streaming + console ports on Public networks too (default = Private/Domain only). Forwarded to both `service install` and `web setup`. Returns a - LEADING SPACE so it concatenates after the preceding {code:...} param without a gap. } + LEADING SPACE so it concatenates after the preceding code-substitution param without a gap. + (Do NOT write a literal code-constant token in this comment: Inno's brace comments do not nest, + so its closing brace would end the comment early and break the [Code] parse.) } function PublicFwParam(Param: String): String; begin if WizardIsTaskSelected('allowpublicfw') then