From 68095b256d0a09460b86e8894e5a2940606affb3 Mon Sep 17 00:00:00 2001 From: Christian Fischer Date: Fri, 26 Jan 2024 07:35:53 +0100 Subject: [PATCH] Doc: Fix typo in nasl-grammar/index.md (#1551) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Juan José Nicola --- doc/manual/nasl/nasl-grammar/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manual/nasl/nasl-grammar/index.md b/doc/manual/nasl/nasl-grammar/index.md index bc6a42f07..f8854cee7 100644 --- a/doc/manual/nasl/nasl-grammar/index.md +++ b/doc/manual/nasl/nasl-grammar/index.md @@ -5,7 +5,7 @@ - A comment starts with a # and finishes at the end of the current line. It is ignored by the lexical analyzer. - “Blanks” may be inserted anywhere between two lexical tokens. A blank may be a sequence of white space, horizontal or vertical tabulation, line feed, form feed or carriage return characters; or a comment. -- Token are parsed by a lexical analyzer and returned to thee parser. +- Token are parsed by a lexical analyzer and returned to the parser. - As the lexical analyzer returns the longer token it finds, expressions like `a+++++b` without any white space are erroneous because they will be interpreted as `a++ ++ + b`, i.e., `(a++ ++) + b` just like in ANSI C . - You have to insert spaces: `a++ + ++b` - You cannot insert spaces in the middle of multiple character tokens, e.g., `x = a + +;` will not parse. Write `x = a ++;`