From a2e1ea009127de8edcde3d1c4860909f273dd460 Mon Sep 17 00:00:00 2001 From: FellippeHeitor Date: Sun, 5 Jan 2020 19:38:22 -0300 Subject: [PATCH] Properly detects OPTION (_)EXPLICIT to set opex_comments. --- source/qb64.bas | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/qb64.bas b/source/qb64.bas index 6f0a3369a..70ad535c9 100644 --- a/source/qb64.bas +++ b/source/qb64.bas @@ -2991,7 +2991,8 @@ DO IF LEFT$(a3u$, 4) = "REM " OR _ (LEFT$(a3u$, 3) = "REM" AND LEN(a3u$) = 3) OR _ LEFT$(a3u$, 1) = "'" OR _ - (LEFT$(a3u$, 7) = "OPTION " AND LEFT$(LTRIM$(MID$(a3u$, 8)), 9) = qb64prefix$ + "EXPLICIT") OR _ + (LEFT$(a3u$, 7) = "OPTION " AND LEFT$(LTRIM$(MID$(a3u$, 8)), 9) = "_EXPLICIT") OR _ + (LEFT$(a3u$, 7) = "OPTION " AND LEFT$(LTRIM$(MID$(a3u$, 8)), 8) = "EXPLICIT" AND qb64prefix_set = 1) OR _ LEFT$(a3u$, 1) = "$" THEN 'It's a comment, $metacommand, or OPTION _EXPLICIT itself, alright. 'But even being a comment, there could be an $INCLUDE in there, let's check: