You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PDT parsers will emit timer names that reflect the scope of the procedure declaration. For example you might have nested internal procedures within a module or a main program:
program main
implicit nonecall greet("sam")
containssubroutinegreet(person)
character(len=*), intent(in) :: person
character(len=:), allocatable :: message
message = get_greeting_for(person)
print*, trim(message)
containsfunctionget_greeting_for(person)
character(*), intent(in) :: person
character(:), allocatable :: get_greeting_for
associate(msg => "Hello "//trim(person)//"!")
allocate(get_greeting_for, source=msg)
end associate
endfunction get_greeting_forendsubroutine greetend program main
PDT seems to declare timers like main::greet and main::greet::get_greeting_for
The text was updated successfully, but these errors were encountered:
well, recent GFortrans don't support nesting multiple contains statements, so this might not be correct code, but, you will still have internal procedures inside of modules and main programs...
The PDT parsers will emit timer names that reflect the scope of the procedure declaration. For example you might have nested internal procedures within a module or a main program:
PDT seems to declare timers like
main::greet
andmain::greet::get_greeting_for
The text was updated successfully, but these errors were encountered: