- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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..."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 :-) !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What if it said "does not exist or is not accessible"? Would that be better?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve Lionel (Intel) wrote:
What if it said "does not exist or is not accessible"? Would that be better?
Yes that would make sense.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Escalated as issue DPD200414838.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The wording will be changed for a future release.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page