preprocessor/src/macro
Sébastien Villemot 487c372900
Macroprocessor: fix newlines in output when under Windows and input uses CR+LF convention
If the input .mod file uses CR+LF convention, and if the user is under Windows,
then the output of the macroprocessor (as given by the “savemacro” option) had
incorrect end of lines: those would be CR+CR+LF.

The reason is that some TextNode(s) internally created by the macroprocessor
would themselves contain CR+LF sequences, which would then be transformed into
CR+CR+LF in the output (because MinGW transforms LF into CR+LF in output
streams).

The fix consists in changing the nature of the EOL token: the parsed text is no
longer attached to it, so that the Bison file now systematically turns it into
a LF inside TextNode(s).

Closes: #80
2021-11-19 14:55:12 +01:00
..
Directives.cc Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Directives.hh Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Driver.cc Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Driver.hh Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Environment.cc Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Environment.hh Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Expressions.cc Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Expressions.hh Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
ForwardDeclarationsAndEnums.hh Use secure URL for link to GNU licenses 2021-06-09 17:21:00 +02:00
Makefile.am Now that we require Bison ≥ 3.2, the stack.hh and position.hh files are no longer generated 2019-08-14 15:36:31 +02:00
Parser.yy Macroprocessor: fix newlines in output when under Windows and input uses CR+LF convention 2021-11-19 14:55:12 +01:00
Tokenizer.ll Macroprocessor: fix newlines in output when under Windows and input uses CR+LF convention 2021-11-19 14:55:12 +01:00