Skip to content

AADL case-insensitive support problem #235

@jeancharles-roger

Description

@jeancharles-roger

Hi, I just discovered spar and the AADL extension, it is really interesting 👍.

In the VSC extension, I have a problem with uppercase keywords. I have the following code with uppercase keywords:

PACKAGE dataflow_Pkg
PUBLIC
WITH HW;
-- ...

I get the following:
Image

Just passing to lowercase, it does present corrects highlighting:
Image

I also checked with the spar cli but strangely returns ok and a full tree:

% spar parse dataflow.aadl
dataflow.aadl: OK
% spar parse dataflow.aadl --tree
=== dataflow.aadl ===
SOURCE_FILE@0..2124
  WHITESPACE@192..194 "\n\n"
  AADL_PACKAGE@194..2119
    PACKAGE_KW@194..201 "PACKAGE"
    WHITESPACE@201..202 " "
    NAME@202..214
      IDENT@202..214 "dataflow_Pkg"
    WHITESPACE@214..215 "\n"
    PUBLIC_SECTION@215..2100
...

The instance command does also return an empty system.

If I pass the whole file in lowercase I get the expected result. Unfortunately the code we use does mix of upper/lower case (which I don't really like but I have to keep 😅).

Here is the complete file for reference.
dataflow.aadl/txt

Kind regards.
ps: I work at Ellidiss and I developed the other AADL VSC extension. I would rather much try to help you build a better extension than mine (and use it) than try to compete.
ps2: Spar is also interesting to me for the instance and render functions. We develop analyzes and simulations for AADL and SysML v2. I will post some other issues one these topics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions