Link Copied
May you please review this with VS integration team at Intel, perhaps in conjuction with the Fortran compiler team?
Please consider the attachment here and illustration below as a minimal reproducer the Intel team can utilize.
To add to OP's post, please consider a trivial module file m.f90 in a Visual Studio project as follows:
module m
integer :: a = 42
integer :: b = 24
end module mAnd a consuming program like so:
use m, only : a
print *, a
endAs mentioned by OP, the USE statement with ONLY clause masks the object in the debugger:
Whereas without the ONLY clause, the debugger identifies the object - see below:
May you please consider a variant of the above case for a quick review with Intel team and comment here?
Consider the module to employ PRIVATE/PUBLIC attributes to control visibility and USEability:
module m
private
integer, public :: a = 42
integer :: b = 24
end module mNow, similar to IFORT and earlier versions of Visual Studio, one can utilize "qualified" names of objects viz. module_name::object_name to watch the objects in the debugger. Interestingly this facility ignores the Fortran language PRIVATE/PUBLIC attributes which can be bothersome to some working in the proprietary codebase.
Are the above two aspects as Intel software teams have intended?
Thank you,
P.S.> A team I work with reported this issue to me upon seeing the original post. The issue is of great concern and it will be highly beneficial if the VS integration team can include a fix for this as soon as possible.
Hi, I did reproduce your observation about the private/public attributes, but couldn't reproduce that with "only"
It still can show the value of a, even I have the "only" specifier in front of it. Did I miss anything ? Do you have the Intel Fortran Expression Evaluator installed ?
I'm using VS2026 and ifx 2025.3.2.
Hi, Please continue to use module::variable in the watch window as a workaround.
I can reproduce your observation now if I only enter "a" instead of "m::a" in the watch window. And if you hover the cursor above the variable during debug, it doesn't show its value. This is indeed somewhat inconvenient.
As far as I can understand now, this seems a deliberate design in the compiler, that for code "use m, only : a", no new variable is created, instead it's replaced with "m::a" during compile time and that's why you see the error "Undefined variable a" when trying to see its value.
I have escalated this issue to the compiler team and will get back once I get any updates.
Hi, I have some updates that the issue has been fixed with the 2026.0 release. Please verify when the package goes public.
Right now, the variable "a" can be resolved in watch window, it also shows up in the locals window and when you hover your cursor on it.
I also had issues with watching variables in debug if specifying "use module, only : var" with VS2022 17.4.x , Intel 2025.3, and FEE 2025.2.2. We also lost the ability to hover over the variable to see the values.
I got the 2026.0 compiler installed last week and the behavior is now worse than 2025.3. Now all module variables, including ones with no "module, only" designation are showing up as undefined. I deleted my .VS folder, full clean build, all extensions up to date, IFEE still latest available as 2025.2.2. Attached is a snapshot of a very simple sample code.
Hi B, just to clarify, did you clean your solution and recompile with 2026.0? Because the behavior your describing is the behavior we saw in 2025.3 and without a clean it might not actually be recompiling. In 2026.0, all module variables cannot be hovered over and all module variables require Module::var in the watch window even if they are within scope from the use module statements. This is a severe debugging regression we are seeing from switching from ifort.
In my picture are side by side watches of 2025.3 and 2026.0.
1. Red boxes: In 2025.3 if a module variable was set within the same file as the subroutine making a "use module, only :" statement, then that variable was watchable with hover over or in the watch window WITHOUT "module::var". No longer working in 2026.0.
2. Blue boxes: (worse in 2026.0) In 2025.3 not using the ", only :" statement allowed us to hover over and watch values without "module::var". In 2026.0, this now appears to also be undefined and we cannot hover over the variable.
3. Green boxes: In both 2025.3 and 2026.0 you cannot hover over nor watch any module variable if its included in a "use module, only:" statement. All module variables require "module::var".
We should be able to watch all module variables that are within scope without having to manually type in "module name::var" into the watch window like we were able to in ifort.
Just for completion sake, I have also attached an image of the same sample solution watch behavior in oneapi 2023 ifort. Everything within scope of the subroutine is easily watchable with or without module::var and everything can be hovered over.
