Hello,
The f6 Link option needs to take into account the linking of modules.
For example I have a program detailer.dcs which uses symcreat.dcs and menuscal.dcs. The latter two symcreat and menuscal are declared as MODULE in the first line of their source code, detailer is declared as a program.
When linking, the first name used by dcl.exe, must be a program. The module names follow seperated by a comma, the list being terminated by the ';'
So the development involves compiling the dco files for each and then creating the .dcx file (In my case detailer.dcx) via the command:
dcl detailer,symcreat,menuscal;
Modules are often developed as PROGRAM in the development testing process; but then will be recompiled as MODULE to form the .dco file.
F1 Init New should simply allow the user to start a new PROGRAM, or MODULE. The inclusion of #include files in a default new application is unnecessary. A lot of the procedures included in the INCLUDE files are now BUILTIN the compiler.
Regards
Rod Walker
The f6 Link option needs to take into account the linking of modules.
For example I have a program detailer.dcs which uses symcreat.dcs and menuscal.dcs. The latter two symcreat and menuscal are declared as MODULE in the first line of their source code, detailer is declared as a program.
When linking, the first name used by dcl.exe, must be a program. The module names follow seperated by a comma, the list being terminated by the ';'
So the development involves compiling the dco files for each and then creating the .dcx file (In my case detailer.dcx) via the command:
dcl detailer,symcreat,menuscal;
Modules are often developed as PROGRAM in the development testing process; but then will be recompiled as MODULE to form the .dco file.
F1 Init New should simply allow the user to start a new PROGRAM, or MODULE. The inclusion of #include files in a default new application is unnecessary. A lot of the procedures included in the INCLUDE files are now BUILTIN the compiler.
Regards
Rod Walker