suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix a bug found by the lexer stress test

Browse Source 
Unfortunately, not the bug I was hoping to find.
This bug appears to be very old, however; perhaps
as old as the colorer itself.
This commit is contained in:
Robby Findler 2013-08-16 21:23:15 -05:00
parent 42566f1dc4
commit 5aeca646d4
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pkgs/gui-pkgs/gui-lib/framework/private/color.rkt
View File

@ -118,7 +118,7 @@ added get-regions
;; The tree of tokens that have been invalidated by an edit
;; but might still be valid.
invalid-tokens ; = (new token-tree%)
;; The position right before the ainvalid-tokens tree
;; The position right before the invalid-tokens tree
invalid-tokens-start ; = +inf.0
invalid-tokens-mode
;; The position right before the next token to be read
@ -479,7 +479,9 @@ added get-regions
(set-lexer-state-invalid-tokens-start!
ls
(+ (lexer-state-invalid-tokens-start ls) tok-end change-length))
(set-lexer-state-invalid-tokens-mode! ls (and orig-data (data-lexer-mode orig-data)))))
(set-lexer-state-invalid-tokens-mode! ls (and orig-data (data-lexer-mode orig-data)))
(when (<= edit-start-pos (lexer-state-current-pos ls))
(set-lexer-state-current-pos! ls (+ (lexer-state-current-pos ls) change-length)))))
((> edit-start-pos (lexer-state-current-pos ls))
(set-lexer-state-invalid-tokens-start!
ls