From dc554dea8adae2f41363632a19cfc236168504c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lars=20K=C3=BChne?= Date: Fri, 23 May 2008 20:58:56 +0000 Subject: [PATCH] fixed spelling --- src/xdocs/config_header.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/xdocs/config_header.xml b/src/xdocs/config_header.xml index 987de35c9..a0741fb1f 100755 --- a/src/xdocs/config_header.xml +++ b/src/xdocs/config_header.xml @@ -270,12 +270,12 @@ line 14: ^ \*/

- Different programming languages have different comment synatx rules, but all of them + Different programming languages have different comment syntax rules, but all of them start a comment with a non-word character. Hence you can often use the non-word character class to abstract away the concrete comment syntax and allow checking the header for different languages with a single header definition. For example, consider the following header specification (note that this is not - the full Apache licence header): + the full Apache license header):

line 1: ^#! @@ -291,7 +291,7 @@ line 6: ^\W*$ Unix shell scripts, or the xml file header of XML files. Set the multiline property to "1, 2" so these lines can be ignored for file types where they do no apply. - Lines 3 throgh 6 define the actual header content. Note how lines 2, 4 and 5 use escapes + Lines 3 through 6 define the actual header content. Note how lines 2, 4 and 5 use escapes for characters that have special regexp semantics.