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 <noreply@anthropic.com>
2026-07-03 15:27:27 +00:00
parent c52ae119e1
commit fbf3fea0c8
1 changed files with 3 additions and 1 deletions
@@ -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