Talk:Compiler/Simple file inclusion pre processor: Difference between revisions
Content added Content deleted
(→wrong language: Or not) |
(→wrong language: removed "why" since a later example covered things) |
||
Line 4: | Line 4: | ||
:You have a point, but by processing the actual language, it compares the language's pre-processor facilities and also how hard pre-processing the source is. |
:You have a point, but by processing the actual language, it compares the language's pre-processor facilities and also how hard pre-processing the source is. |
||
:I strongly suspect that the syntax of Algol 68, PL/1 and COBOL (for example) makes the implementation harder than a C pre-processor would be, which was part of my motivation. |
:I strongly suspect that the syntax of Algol 68, PL/1 and COBOL (for example) makes the implementation harder than a C pre-processor would be, which was part of my motivation. |
||
:: Why? --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 20:23, 6 June 2021 (UTC) |
|||
::: It offers a comparison of how language design issues interact with language implementation issues, amongst other things. --[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 21:42, 6 June 2021 (UTC) |
|||
:To pre-process Algol 68, PL/1 and COBOL for this task requires some level of lexical analysis, whilst a C pre-processor need only find lines that start with "#include" ( possibly with spaces before and after the "#" ). --[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 18:25, 6 June 2021 (UTC) |
:To pre-process Algol 68, PL/1 and COBOL for this task requires some level of lexical analysis, whilst a C pre-processor need only find lines that start with "#include" ( possibly with spaces before and after the "#" ). --[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 18:25, 6 June 2021 (UTC) |