-
Notifications
You must be signed in to change notification settings - Fork 65
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
Compatibility mode for older VHDL standards #153
Comments
VHDL 2008 standard defines |
Unfortunately it is also a keyword for non-PSL:
|
So to solve this you probably have to declare that the library and or file is not VHDL 2008 in the |
I could add a 2002-compatibility flag at the library granularity in the |
Oh, I didn't know this. |
If you need it someone else probably also does. There is a lot of legacy code in this domain. I will add it in the near future. Can you confirm that it would work for you to set the 2002 compatability the library granularity? Adding it at the file granularity is more work. |
Yes it would work on a library level for me, since all files use an older VHDL standard. |
Hello @kraigher. We currently have the same problem. Are you planning to solve this in the near future? Or is it more work than previously assumed? btw: For us, it would also work at library level. |
It is probably not much work but I have not priortized it so far. This is the type of issue where I would like new contributors to step up as it is an easy first task. I might do it myself as well if I feel the inspiration. As this is just an unpaid hobby project for me I cannot make any promises. |
This has been implemented as part of #284 |
I work with a legacy project and on some entities one of the generics is named "DEFAULT". This gives the following error message:
A minimal example to reproduce the behavior is the following:
It does not matter if "default" is written in capital letters or not. As far as I know, there is no reserved keyword "default" in VHDL. Xilinx ISE also has no problem with it.
Could it be, that it is a keyword in Rust which leads to this error?
By the way: Kudos for creating and maintaining this project. I use it daily and it makes working with VHDL a charm!
The text was updated successfully, but these errors were encountered: