From ef34c0765489dbb6bc8efbe1737208811fc6e1d7 Mon Sep 17 00:00:00 2001 From: kichik Date: Wed, 4 Jul 2007 17:52:47 +0000 Subject: [PATCH] better explain what compiler flags mean and how flow control instructions should be used around them git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@5186 212acab6-be3b-0410-9dea-997c60f758d6 --- Docs/src/compilerflags.but | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/Docs/src/compilerflags.but b/Docs/src/compilerflags.but index 1cac72d6..91ffdd5d 100644 --- a/Docs/src/compilerflags.but +++ b/Docs/src/compilerflags.but @@ -1,6 +1,25 @@ \S1{flags} Compiler Flags -The following commands change how the compiler generates code and compresses data. Unless otherwise noted, these commands are valid anywhere in the script, and effect every line below where each one is placed (until overridden by another command). +The following commands affect how the compiler generates code and compresses data. Unless otherwise noted, these commands are valid anywhere in the script, and effect every line below where each one is placed (until overridden by another command). They cannot be jumped over using \R{flowcontrol}{flow control insutrctions}. + +For example, in the following script, blah.dat will never be overwritten. + +\c ${If} $0 == 0 +\c SetOverwrite on +\c ${Else} +\c SetOverwrite off +\c ${EndIf} +\c File blah.dat # overwrite is always off here! + +Instead, the following should be used. + +\c ${If} $0 == 0 +\c SetOverwrite on +\c File blah.dat +\c ${Else} +\c SetOverwrite off +\c File blah.dat +\c ${EndIf} \S2{asetallowskipfiles} AllowSkipFiles