GRECLIPSE

Slashy string '/' breaks color coding

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.5.6
  • Fix Version/s: 2.0.2Release
  • Component/s: Inferencing Engine
  • Labels:
    None
  • Environment:
    Eclipse 3.3.2 on Windows Xp pro SP2
  • Number of attachments :
    1

Description

I could not find this reported elsewhere. Here is a regex:

String regExSqlCreate = /create table [a-z".]*($

{table}[\r\n\d\w\s_,();]+)revoke all on [a-z\".]*${table}

from "public"/

As the attached picture shows 'create table [a-z' shows in black, and 'public' shows in keyword color.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. GRECLIPSE-251 Slashy strings don't like escaped slash at the end

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Bug - A problem which impairs or prevents the functions of the product. GRECLIPSE-248 When using the divide operator '/' every that follows in that line is displayed as String coloring

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Hide
Permalink
Andrew Eisenberg added a comment -

Fixed now. In the latest dev build, slashy strings are no longer handled by the GroovyTagScanner, but rather by the semantic highlighter. This means that we look at the AST to figure out where the slashy strings are; we don't use a scanner. And as long as the file is parseable, we can be certain that we are only highlighting the correct parts of the text. Unfortunately, if the text is not parseable, then we don't highlight anything. I think this is a reasonable limitation.

Show
Andrew Eisenberg added a comment - Fixed now. In the latest dev build, slashy strings are no longer handled by the GroovyTagScanner, but rather by the semantic highlighter. This means that we look at the AST to figure out where the slashy strings are; we don't use a scanner. And as long as the file is parseable, we can be certain that we are only highlighting the correct parts of the text. Unfortunately, if the text is not parseable, then we don't highlight anything. I think this is a reasonable limitation.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    tom corcoran
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: