-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
77 additions
and
68 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
Rebol [] | ||
|
||
; Fixed issues - kept here for regression checking | ||
; | ||
; So below should all work now :) | ||
|
||
literal: [the'end] | ||
|
||
ok_filename: %file%20with%20space.txt | ||
bad_filename: %"file with space.txt" ; probably best as this anyway | ||
also: %1111.txt ; allows leading numbers | ||
|
||
tuples: [333.333.333 444.444.444.444 555.555.555.555.555] ; only defined 3 & 4 tuples at moment | ||
|
||
; Decided to make set-word! RE tighter so avoid pollution elsewere | ||
; NB. (though original did seem fine without this check) | ||
bad-setword:[print "must have space before block"] | ||
good-setword: [print "I'm all good"] | ||
|
||
|
||
; some keyword issues | ||
|
||
print["must be space after keyword to highlight it"] | ||
print ["this works fine"] | ||
|
||
; and will (nearly) always highlight word as keyword (often useful indicator!) | ||
print: func [replace] [print replace] ; this is all fine (by luck!) | ||
print: func [replace x] [print [replace x]] ; this time "replace" is hi-lighted as keyword | ||
foo: does [print] | ||
; NB - Keywords will be highlighted as keyword when preceded by whitespace | ||
|
||
; refinements! have issues so not included | ||
ref: [/refinement] | ||
|
||
|
||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | ||
; other edge cases just have to live with (for now) | ||
|
||
xxx-replace: xxx-replace - no-xxx-replacethis-xxxreplace-foo ; \b JS issue | ||
|
||
; number datatypes funnies | ||
num1: num2 + num2for | ||
|
||
; set-word! path! | ||
block/(1 + baz/1): constants/(1 + length? foo) | ||
|
||
; type! issues | ||
num!ber: num!ber + 1 | ||
|
||
|
||
|
||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | ||
; not implemented but may do in future | ||
|
||
; see undefined types in GCP-datatypes.r | ||
; utf-8 usage | ||
|
||
|
||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | ||
; tag! - Can't do :( | ||
; * GCP doesn't like html tags unless they're escape | ||
; * ref: http://stackoverflow.com/questions/7787834/using-google-prettify-to-display-html-and-css-code-do-i-have-to-replace-every | ||
|
||
|
||
; below should highlight correctly! (just a highlighting placeholder!) | ||
print "hello world" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,3 +3,4 @@ mv lang-rebol.js .. | |
mv not-working.html .. | ||
mv real-example.html .. | ||
mv all-keywords.html .. | ||
mv fixed.html .. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters