forums.silverfrost.com

m.burkhardt · Joined: 02 Sep 2008 Posts: 26

Is it possible to change Variable values at debug time?
I'll make a break and after arriving this break I'll change the content of an variable value! Is this possible in plato?
I receive the info that this is NOT possible in VS201 environment in FTN95 Silverfrost Version 6.
Is this right?

Kind regards
Michael

jjgermis · Posted: Fri Sep 09, 2011 12:17 pm Post subject:

This is an interesting question! The most debuggers that I have used in the past do not have this option. Why not just add a line of code to change the variable to the desired value?

PaulLaidler · Posted: Sat Sep 10, 2011 9:08 am Post subject:

I don't know of any way to change the variables via SDBG at runtime (other than via the code).

brucebowler · Guest

Unless I'm missing something, doesn't "Tools>>command prompt..." let you do that with "let variable=expression"?

Bruce

PaulLaidler · Posted: Tue Sep 13, 2011 2:53 pm Post subject:

Yes you are right. I had forgotten about that feature.

jjgermis · Posted: Tue Sep 13, 2011 3:02 pm Post subject:

It works - a feature I never knew! One should however use the correct syntax for the command.

felix · Joined: 09 Aug 2011 Posts: 5

I was hoping for something like a compiler directive like "EQUATE" in other languages, especially assemblers. Consider....

EQUATE (value,80)

OPEN (UNIT=LU19,FILE='FILEADIR.TXT',RECL=value,ERR=8, &
ACCESS="DIRECT",FORM="FORMATTED",STATUS="NEW")

PaulLaidler · Posted: Thu Nov 03, 2011 9:30 am Post subject:

In what way is that different from a simple Fortran assignment statement..

value = 80

LitusSaxonicum · Posted: Thu Nov 03, 2011 2:24 pm Post subject:

Paul,

Just an idea: does he mean the EQUATE bit to be something you type into the debugger, and the following Fortran code to be how the program uses it?

E

felix · Joined: 09 Aug 2011 Posts: 5

Sorry, I chose the wrong variable in the Open statement. Should have been the ERR instead of the RECL.

I = 80
OPEN.................ERR=I.........

E:\FORTRAN JOBS\JOINABMM.F95(260) : error 525 - Invalid character 'I' after ERR
E:\FORTRAN JOBS\JOINABMM.F95(260) : error 517 - Labels must not be zero (0)
Compilation failed.

The EQUATE (or similar) statement should be universal across all "languages" including scripts. The purpose of the EQUATE statement is the exchange of SYMBOLS, not necessarily values like was exemplified by Paul.

An EQUATE statement immediately after the opening identification statement (PROGRAM,SUBROUTINE,FUNCTION,etal) of the program would take care of this problem as shown. Better yet, the statement should be a compiler directive instead and be among the first lines the compiler sees BEFORE any language statements.

PaulLaidler · Posted: Fri Nov 04, 2011 8:44 am Post subject:

The FTN95 help file (FTN95.chm) describes Conditional Compilation (VPARAM and SPARAM) and also C-Style preprocessing (#define etc).