Remove excess blank lines

[ocean] / csrc / scanner.mdc

diff --git a/csrc/scanner.mdc b/csrc/scanner.mdc
index 705e02e096939e4b20e3e3ad4da5a91264d107a3..42001ff895b0196a7ab83e30afb5c50b5eae1cf0 100644 (file)
--- a/csrc/scanner.mdc
+++ b/csrc/scanner.mdc
@@ -85,7 +85,6 @@ from token to token.
 ###### token_next init
        int ignored = state->conf->ignored;
 
 ###### token_next init
        int ignored = state->conf->ignored;
 

-

 The different tokens are numbers, words, marks, strings, comments,
 newlines, EOF, and indents, each of which is examined in detail below.
 
 The different tokens are numbers, words, marks, strings, comments,
 newlines, EOF, and indents, each of which is examined in detail below.
 


@@ -805,7 +804,6 @@ information and return one token.
                continue;
        }
 
                continue;
        }
 

-

 ###### delayed tokens
 
        if (state->check_indent || state->delayed_lines) {
 ###### delayed tokens
 
        if (state->check_indent || state->delayed_lines) {


@@ -848,7 +846,6 @@ tokens will continue to return the same end-of-file token.
 ###### token types
        TK_eof,
 
 ###### token types
        TK_eof,
 

-

 ###### white space
        if (ch == WEOF) {
                if (state->col) {
 ###### white space
        if (ch == WEOF) {
                if (state->col) {


@@ -1093,7 +1090,6 @@ parsed too much already.  For that there is `reset_token`.
                tok->txt.len = 0;
        }
 
                tok->txt.len = 0;
        }
 

-

 Tokens make not cross into the next `code_node`, and some tokens can
 include the newline at the and of a `code_node`, we must be able to
 easily check if we have reached the end.  Equally we need to know if
 Tokens make not cross into the next `code_node`, and some tokens can
 include the newline at the and of a `code_node`, we must be able to
 easily check if we have reached the end.  Equally we need to know if


@@ -1525,7 +1521,6 @@ character `expc`.
        tok.txt += d;
        tok.len -= d;
 
        tok.txt += d;
        tok.len -= d;
 

-

 Now that we have the mantissa and the exponent we can multiply them
 together, also allowing for the number of digits after the decimal
 mark.
 Now that we have the mantissa and the exponent we can multiply them
 together, also allowing for the number of digits after the decimal
 mark.


@@ -1589,7 +1584,6 @@ Now we are ready to parse a number: the base, mantissa, and exponent.
 If all goes well we check for the possible trailing letters and
 return.  Return value is 1 for success and 0 for failure.
 
 If all goes well we check for the possible trailing letters and
 return.  Return value is 1 for success and 0 for failure.
 

-

 ###### number functions
        int number_parse(mpq_t num, char tail[3], struct text tok)
        {
 ###### number functions
        int number_parse(mpq_t num, char tail[3], struct text tok)
        {


@@ -1924,7 +1918,6 @@ String parsing goes in `libstring.c`
        libstring.o : libstring.c
                $(CC) $(CFLAGS) -c libstring.c
 
        libstring.o : libstring.c
                $(CC) $(CFLAGS) -c libstring.c
 

-

 ## Testing
 
 As "untested code is buggy code" we need a program to easily test
 ## Testing
 
 As "untested code is buggy code" we need a program to easily test