Line breaks cannot be placed arbitrarily without breaking highlighting

[jdghunt]

Line breaks cannot be placed where desired due to highlighting limitations.

For example, consider:

const ram_addr_t[5] SRAM_OFFSETS = {9'd0,
                                    9'd256,
                                    9'd256 + 9'd64,
                                    9'd256 + 9'd64 + 9'd16,
                                    9'd256 + 9'd64 + 9'd16 + 9'd4};

vs

const ram_addr_t[5] SRAM_OFFSETS = {9'd0, 9'd256, 9'd256 + 9'd64, 9'd256 + 9'd64 + 9'd16, 9'd256 + 9'd64 + 9'd16 + 9'd4};

Both of these are legal, but the former is probably preferable for readability but doesn't highlight.

Similar issues exist with most of the language constructs. Fixing this requires a fundamental change in how the regexes are written given that the Textmate regexes do not support multi-line constructs. In essence, begin/end match systems must be used instead of .* in various places etc.

[jdghunt]

A further example:

network foo {
  param bool FOO_PARAM = 0;
  import bool foo_check(bool v);
  new fsm bar {
    bool val;
    void main() {
      val = false;
      gen if (FOO_PARAM) {
        if  (val) { assert foo_check(val);  }
      }
      val = true; // not highlighted
      fence;
    }
  }
}

Example with broken highlighting:

Example with correct highlighting:

For the benefit of whoever ends up fixing this, inspection using the highlighter debugger reveals that in the bad case the line val = true; is thought to be just outside the fsm body, which is why it doesn't get highlighted in that case. The root cause of this is that the pattern that matches the body of the if condition is greedy, and matches up the first opening ( on the if line with the ) that closes the assertion condition, not the end of the if condition. Proper begin/end matching is required for the parentheses around the condition I think.