I think I get what a static signal is, but I'm not clear on what exactly is wrong. They refer to the "actual" which is the value passed into the function, no? What is not static about "Buttons"??? Is it the fact that the value is not known until thecode is run??? This error goes away when I remove the signal designation from the declaration of parameters, but then it barfs on using it to invoke the falling_edge function because it's not a signal.
On Monday, September 21, 2020 at 11:07:37 AM UTC-4, gnuarm.del...@gmail.com wrote:code is run??? This error goes away when I remove the signal designation from the declaration of parameters, but then it barfs on using it to invoke the falling_edge function because it's not a signal.
I think I get what a static signal is, but I'm not clear on what exactly is wrong. They refer to the "actual" which is the value passed into the function, no? What is not static about "Buttons"??? Is it the fact that the value is not known until the
It's not 'Buttons' that the complaint is about, but 'Buttons(index)' which is the input parameter to the falling_edge function. 'Buttons(index)' is not static, hence the complaint. I don't know what problem this VHDL rule is addressing with the rule,but thought I'd clarify the actual complaint in case someone else might know the reason for the rule.
Kevin Jennings
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 86:58:53 |
Calls: | 6,658 |
Files: | 12,203 |
Messages: | 5,333,878 |