From 5fdc37e2e3962f8078a77a6c14b9be0de4628762 Mon Sep 17 00:00:00 2001 From: sof Date: Thu, 5 Jun 1997 20:45:33 +0000 Subject: [PATCH] [project @ 1997-06-05 20:45:33 by sof] Added SOURCE pragma handling; moved -- comment rule to have it kick-in on -- --- ghc/compiler/parser/hslexer.flex | 45 ++++++++++++++++++++++---------------- 1 file changed, 26 insertions(+), 19 deletions(-) diff --git a/ghc/compiler/parser/hslexer.flex b/ghc/compiler/parser/hslexer.flex index f7da732..dac635e 100644 --- a/ghc/compiler/parser/hslexer.flex +++ b/ghc/compiler/parser/hslexer.flex @@ -7,7 +7,8 @@ * * **********************************************************************/ -#include "../../includes/config.h" +/* The includes/config.h one */ +#include "config.h" #include @@ -254,6 +255,23 @@ NL [\n\r] %% %{ + /* + * Simple comments and whitespace. Normally, we would just ignore these, but + * in case we're processing a string escape, we need to note that we've seen + * a gap. + * + * Note that we cater for a comment line that *doesn't* end in a newline. + * This is incorrect, strictly speaking, but seems like the right thing + * to do. Reported by Rajiv Mirani. (WDP 95/08) + * + * Hackily moved up here so that --<> will match -- SOF 5/97 + */ +%} + +"--"[^\n\r]*{NL}?{WS}* | +{WS}+ { noGap = FALSE; } + +%{ /* * Special GHC pragma rules. Do we need a start state for interface files, * so these won't be matched in source files? --JSM @@ -308,15 +326,18 @@ NL [\n\r] PUSH_STATE(Comment); } "{-#"{WS}*"OPTIONS" { - /* these are by the driver! */ + /* these are for the driver! */ nested_comments =1; PUSH_STATE(Comment); } -"{-#"{WS}*"SOURCE" { - /* these are used by `make depend' (temp) */ +"{-#"{WS}*"SOURCE"{WS}*"#"?"-}" { + /* these are used by `make depend' and the + compiler to indicate that a module should + be imported from source */ nested_comments =1; - PUSH_STATE(Comment); + RETURN(SOURCE_UPRAGMA); } + "{-#"{WS}*[A-Z_]+ { fprintf(stderr, "%s:%d: Warning: Unrecognised pragma '", input_filename, hsplineno); @@ -767,20 +788,6 @@ NL [\n\r] POP_STATE; } -%{ - /* - * Simple comments and whitespace. Normally, we would just ignore these, but - * in case we're processing a string escape, we need to note that we've seen - * a gap. - * - * Note that we cater for a comment line that *doesn't* end in a newline. - * This is incorrect, strictly speaking, but seems like the right thing - * to do. Reported by Rajiv Mirani. (WDP 95/08) - */ -%} - -"--".*{NL}?{WS}* | -{WS}+ { noGap = FALSE; } %{ /* -- 1.7.10.4