Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

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

andrew_4619
Honored Contributor II
2,784 Views

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.

 

 

 

0 Kudos
6 Replies
NotThatItMatters
Beginner
2,784 Views

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..."

0 Kudos
andrew_4619
Honored Contributor II
2,784 Views

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 :-) !

 

 

0 Kudos
Steven_L_Intel1
Employee
2,784 Views

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

0 Kudos
andrew_4619
Honored Contributor II
2,784 Views

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

Yes that would make sense.

0 Kudos
Steven_L_Intel1
Employee
2,784 Views

Escalated as issue DPD200414838.

0 Kudos
Steven_L_Intel1
Employee
2,784 Views

The wording will be changed for a future release.

0 Kudos
Reply