The information in this article applies to:
SYMPTOMSRenamed USE-associated module variables cannot be referenced or displayed in the debugger. The debugger will only reference and display the original module variable names, not the renamed module variable aliases created with the USE statement's module variable renaming specifier (=>). STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATIONIn the sample code provided, the module's public variable G is renamed by the USE statement and is known in the internal procedure as the alias access variable H. However, the debugger incorrectly reports the wrong USE variable G in the locals window, so attempting to view the value of H in the watch window causes the message, "undefined variable." Steps to Reproduce Problem
Additional query words: 4.00
Keywords : kbFortranPS kbLangFortran |
Last Reviewed: November 1, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |