This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 321750 - [SSE] keyword "to" is not highlighted
Summary: [SSE] keyword "to" is not highlighted
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: WTP Incubator (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Lionel Villard CLA
QA Contact: XQDT CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-04 11:51 EDT by Gabriel Petrovay CLA
Modified: 2021-11-18 16:19 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel Petrovay CLA 2010-08-04 11:51:49 EDT
Test the following expression:
1 to 3
Comment 1 Gabriel Petrovay CLA 2010-08-05 05:50:49 EDT
The problem appears in more cases starting with 	OrExpr in the EBNF: or, and, to, div, mod, idiv, union, ...
Comment 2 Lionel Villard CLA 2010-08-05 07:54:28 EDT
(In reply to comment #1)
> The problem appears in more cases starting with 	OrExpr in the EBNF: or, and,
> to, div, mod, idiv, union, ...

can you be more explicit and give examples? Thanks.
Comment 3 Gabriel Petrovay CLA 2010-08-05 09:00:47 EDT
1 to 2
2 div 3
3 union 4
4 and 5
etc
Comment 4 Lionel Villard CLA 2010-08-05 09:25:18 EDT
Currently, operators are not highlighted. Go to Preferences -> XQuery -> Editor -> Syntax hightlighting and change the defaut for operator.
Comment 5 Gabriel Petrovay CLA 2010-08-05 11:05:30 EDT
I think that the operators that are not "special-sign-only" ("div", "to", "union", etc) should be marked as keywords for syntax coloring. Think about the "new" operator in C++.

I think this is helpful for examples like:

let $x := treat treat as node()

if the operators remain with the default black color.

-----

On the other hand, I would not like to see all signs marked as keywords.
Comment 6 Lionel Villard CLA 2010-08-06 17:14:56 EDT
This is fixed.
Comment 7 Gabriel Petrovay CLA 2010-08-25 11:27:26 EDT
Makes it to the 0.8M1 release.