Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anyone using non-instantiated signal (instantiate: false) #666

Open
erikbosch opened this issue Oct 5, 2023 · 1 comment
Open

Anyone using non-instantiated signal (instantiate: false) #666

erikbosch opened this issue Oct 5, 2023 · 1 comment

Comments

@erikbosch
Copy link
Collaborator

The instantiate: false attribute is described in VSS documentation but not actively used in current VSS standard catalog. It is intended to give something similar to C++ static class members, but that is not always easy to represent in all target environments/formats, i.e. not necessarily easy to support in all existing or future vss-tools. By that reason I would like to know:

  • Is there someone using instantiate: false in their own (private) VSS implementation?
  • If not, would be a candidate for removal, or alternatively state that it not will be accepted in standard catalog (i.e. error when using --strict mode)?

https://covesa.github.io/vehicle_signal_specification/rule_set/instances/#how-can-i-exclude-child-nodes-from-instantiation

# Cabin.vspec
Door:
  type: branch
  instances:
    - Row[1,2]
    - ["DriverSide","PassengerSide"]
  description: All doors, including windows and switches
#include SingleDoor.vspec Door

Door.SomeSignal:
  datatype: uint8
  type: attribute
  instantiate: false
  description: A door signal that should not be instantiated.
@ppb2020
Copy link
Collaborator

ppb2020 commented Oct 6, 2023

I can confirm we are not using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants