Debian Codegraph @

system/ftoc/doc/modules.txt

raw
1
2 1) ftoc_names.for + ftoc_namesc.c => ftoc_names.exe
3
4 find out how Fortran subroutine names like CSUB() are passed on
5 to C
6 the executable prints out the string (3/4 chars):
7 -fl for csub() -fu for CSUB()
8 -fl_ for csub_() -fu_ for CSUB_()
9 -_fl_ for _csub_() -f_u_ for _CSUB_()
10 -_fl for _csub() -f_u for _CSUB()
11
12 e.g. on AMD 64 Athlon +3500 with SUSE 9.3, gcc 3.3 we get
13 $ ../exec/ftoc_names.exe
14 -fl_
15
16 2) forif.c + ftoc.c => forif.exe
17
18 convert a .fc file to a regular .c file
19 using output from ftoc_names.exe as input
20
21
22 3) ftoc_log.for + ftoc_logc.fc => ftoc_log.exe
23
24 to determine the integer values given to .TRUE. and .FALSE. in Fortran
25 as the type .fc indicates, ftoc_log.exe already uses the interface
26 F77-C determined before...
27
28
29 4) for_try.for + ftoc_stack.fc + stack_dump.h => ftoc_stack.exe
30
31 to show the parameter stack for different subroutine calls from
32 Fortran, inside the called C routine
33
34 the program is controlled via the ASCII file stack-test (1 line)
35 which contains a control-flag, the 1st and last stack entry to be
36 displayed
37
38 within the C routines of ftoc_stack.fc, the flags nogo[i] are set
39 = 0 (just show bare stack), = 1 (interpret entry as holding a
40 character parameter), = 2 (look for integer parameters).
41
42
43 5) for_test.for + ftoc_test.fc => ftoc_test.exe
44
45 test calling C routines from Fortran, i.e.
46 SSP1(s1,n1,s2,n2), SSP2(n1,n2,n3,n4,n5,n6), and SSP3(s1,s2,s3)
47
48 compare numbers, strings and lengths of strings with original values
49 from the Fortran main program
50
51
52
53 060228
54