X-Git-Url: https://ocean-lang.org/code/?p=ocean;a=blobdiff_plain;f=csrc%2Fscanner.mdc;h=42001ff895b0196a7ab83e30afb5c50b5eae1cf0;hp=705e02e096939e4b20e3e3ad4da5a91264d107a3;hb=5107f51f1ba2b12dbffef31403ebfea30688b96b;hpb=744a59663bace6a4d9db58ec97c4cf9aa24082a9

diff --git a/csrc/scanner.mdc b/csrc/scanner.mdc
index 705e02e..42001ff 100644
--- a/csrc/scanner.mdc
+++ b/csrc/scanner.mdc
@@ -85,7 +85,6 @@ from token to token.
 ###### 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.
 
@@ -805,7 +804,6 @@ information and return one token.
 		continue;
 	}
 
-
 ###### 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,
 
-
 ###### 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;
 	}
 
-
 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;
 
-
 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.
 
-
 ###### 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
 
-
 ## Testing
 
 As "untested code is buggy code" we need a program to easily test