This folder is an attempt to construct a dll that can be used by nlfit. The poly routine is usually all that changes in going from one fit to another. If this is made into a dll, this is the only part that needs to be compiled. In addition it can be compiled in Fortran, in C or even Pascal if the proper rules are followed. The folders are the current attempts to make the main code simulate nlfit and the dll poly. The zips are the simplest example of the calls described.
1. WforWfor Welcome.htm Watcom Fortran calls Dll made by Watcom Fortran.
2. Ifort ifort.htm Intel-10 Fortran calls Dll made by Intel-10 Fortran.
4. IfWRaExe Welcome.htm Intel-10 Fortran calls a poly executable made by Watcom Fortran.
5. IfWfRA Welcome.htm Intel-10 Fortran calls a Watcom poly dll whose arguments are passed through the file test.out. This is the goal originally set for the use of dll’s.
6. WforWc Welcome.htm WforWc.zip Watcom Fortran calls Dll made in C. – uses pragma This is the recommended form. Watcom built both the C and the Fortran compiler. All parameters pass internally without the overhead of the file test.out.
7. WforBc Welcome.htm Watcom Fortran calls Dll made by Borland C – has not worked yet.
8. WccWc Welcome.htm WccWc.zip Watcom C code calls Dll made in C
9. WccWfor Welcome.htm WccWfor.zip Watcom C code calls Dll made in Fortran – uses pragma
10. Cwfort Cwfort\notes.txt – C code calls Fortran code.
A lot of system overhead is hidden
in the executables and dll’s normally
constructed. A hint of these is in WcomFortDLLs.htm which is taken from a section of fbooks.hlp.