http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Joost.VandeVondele at mat
| |dot ethz.ch
--- Comment #2 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch>
2012-10-27 17:38:34 UTC ---
(In reply to comment #1)
> How about the following (which of course implies that the users didn't intent
> to use an array - if they did, Intel's becomes more helpful.)
Indeed, I was coding this with the intent of declaring it as an array, no
doubt, passing an array is much more common than passing a procedure. Note that
intel's location is also more useful in that case. I think the usefulness of
Intel's message lies in the fact that it suggests the common cause of the
error. Even with the experience I have, I first started to look for a procedure
with the same name as the variable.
