gwennkoi / vscode-lpc-lang Goto Github PK

Thanks for this extension! I lack the time to delve into the details of how it all works so thought I'd ask here: Is it feasible to build in support for multi-line string literal blocks?

Example:

    set("long",@EndText
    This is a really long description that spans multiple lines and
may have some single-quote apostrophes in it. It's my hope that
those apostrophes can be set to be included in this block of text!
EndText
    );

This is the convention we use in our system frequently. But the entire syntax highlighting
gets broken by those 's.

Describe the bug
When a super call contains a reserved keyword, it is highlighted when normally it would not.

Expected behavior
super:: calls shouldn't highlight reserved words.

Screenshots

LPC Code

inherit "/std/object.c";
inherit "/std/something.c";
void fn () {
    object::fn();       // object is highlighted like a variable
    something::fn();    // working as expected
}

VS Code Version:
Version: 1.78.2

OS: [e.g. Windows 10, MacOS, Arch Linux]
Windows 10

Additional context
vscode-lpc-lang v1.1.4

Copying from @gesslar's issue report here jlchmura/prettier-lpc-vscode#18

set("long", @text

   The soft, black and white pelt has been expertly cured to preserve the 
texture and hairs of the panda's fur. Though the skin is quite beautiful,
the animal itself must have been even more majestic.

text
);

When the marker (in this case text) appears in another word at the start of a line (texture on the 4th line), the highlighting ends there instead of at the actual end marker.

Whenever I use this extension and use mapping ([ ]) or array ({ }) symbols, the extension creates an additional closing paren at the end. See attached image.

Hi,
How compatible/in-sync is this with the LDMud (post LP) driver? I know you are updating with Fluff in mind, which is based off of MudOS... If I want one more suitable to LDMud (which is based off LPMud/Amylaar, not MudOS), would it make more sense to do my own starting with your Pike version? I'm not sure, but it seems like Pike might be even more out of date in terms of compatibility with LDMud?

Since the 1.0.0 update where "Strings are now handled by the language server" strings are context-highlighted even within comment blocks. This means that an apostrophe in a comment block starts a string, then it extends several lines or to the end of the file.

The regex is detecting keywords in the middle of a string literal.

For example, finding for in the middle of the string literal in the accompanied screenshot.