Too permissive syntax in writeln()
## Summary
<!-- Summarize the bug encountered concisely -->
The compiler do not complain when encountering an wrong statement in writeln()
## System Information
<!-- The more information are provided the easier it is to replicate the bug -->
- **Operating system:** <!-- Windows, Linux (if possible, also name the distro), FreeBSD, Android, ... --> both linux 64 bits (Mageia) and Windows10 32 bits
- **Processor architecture:** <!-- x86, x86-64, ARM, AARCH64, AVR, RISC-V, PowerPC, ... --> Intel x86
- **Compiler version:** <!-- 3.2, 3.2.2, 3.3, trunk, beta, ... (if possible, give also the git hash) --> 3.2.2
- **Device:** <!-- Computer, Tablet, Mobile, Amiga, Microcontroller, ... --> Laptop
## Steps to reproduce
<!-- How one can reproduce the issue - this is very important! -->
Try to compile the following program
```pascal
PROGRAM doublepoint;
{$APPTYPE CONSOLE}
VAR
F: TEXT;
BEGIN
ASSIGN(F, 'doublepoint.txt');
REWRITE(F);
WRITELN(F, 'Hello'); { ',' is legal - compiler just do its job }
WRITELN(F: 'Hello'); { ':' is not legal - compiler should emit an error, but 3.2.2 fail to }
CLOSE(F);
END.
```
The compilation should fail due to the second Hello line where ':' is not allowed by definition.
3.2.2 compile without complaining ; he should stop compiling.
## Example Project
<!-- If possible, please create an example project that exhibits the problematic
behavior, and link to it here in the bug report. -->
See above.
## What is the current bug behavior?
<!-- What actually happens -->
Compile without complaining.
## What is the expected (correct) behavior?
<!-- What you should see instead -->
The compiler should complain and stop the job.
## Relevant logs and/or screenshots
<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as
it's very hard to read otherwise.
You can also use syntax highlighting for Pascal with: ```pascal the code```
For more information see https://docs.gitlab.com/ee/user/markdown.html -->
## Possible fixes
<!-- If you can, link to the line of code that might be responsible for the problem -->
After @PascalDragon: most probably linked to the parsing of the code for numerical output as 3.1415:5:2, but not legal for an assigned textfile.
issue