error #6580: Name in only-list does not exist.

[andrew_4619]

Yes, yes I know, age, brain fade, etc.....

Checked the Submodule interface, checked the module subroutine declaration, did a clean and rebuild, same problem...

I think 'error #xxxx: Name in only-list is PRIVATE' would be a better message.

[NotThatItMatters]

Age, brain fade, etc. I have had the same problem, but the quick solution has always been "What, I know the name exists? Look here's the name! Wait, it is PRIVATE.  Duh..."

[andrew_4619]

NotThatItMatters wrote:
Age, brain fade, etc. I have had the same problem, but the quick solution has always been "What, I know the name exists? Look here's the name! Wait, it is PRIVATE.  Duh..."

Whilst I don't disagree with you I still think an error message that is correct is better than one that is incorrect. This is not however going to change my life :-) !

[Steven_L_Intel1]

What if it said "does not exist or is not accessible"? Would that be better?

[andrew_4619]

Steve Lionel (Intel) wrote:
What if it said "does not exist or is not accessible"? Would that be better?

Yes that would make sense.

[Steven_L_Intel1]

Escalated as issue DPD200414838.

[Steven_L_Intel1]

The wording will be changed for a future release.