Quickfix of missing port
I just 'wasted' some time on a quickfix problem, which might be related to others already posted in this forum:
Imagine a instance with a port map sporting a signal 'too much', i.e. missing in the port definition of entity and component.
The problem is flagged as 'could not find declaration of signal' and quickfix offers to 'generate signal declaration'. This should have made me suspicious, since the signal in question is in the port map's left column.
But I tried it anyway, with the result, that nothing happened (apparently).
So I went on adding the port manually, but the problem marker still did not disappear.

I found that the attempt to quickfix had created an incomplete signal declaration (which also created a problem marker that I overlooked) which conflicted with my manual update to the port definition. But as already posted by Simon, multiple declarations are reported as 'missing' instead of 'ambiguous', leading to my 'waste of time' :-)
But anyway, quickfix should update the port definition. Adding a signal is not the right fix in this case.
Regards,
Kurt.
- Forums:
quickfix needs more intelligence
Hi Kurt,
I'm sorry about the confusion.
Our current QuickFix implementation is not as smart as it should be. We should have several different behaviors (new signal, new constant, new port, ...) depending on the context. This is a known issue (ticket:394).
This obvious workaround is to pay close attention when using quickfix, but I would agree the tool is really at fault here.
Philippe
Post new comment