Hi Pietro
Some thoughts on XBuilder.( Pietro Moras's Classic Dcal program editor).
The menu item 'S3 *DCO_MGR' should be placed before 'F6 Link'. Better still when the active file is a module file then the Link option should not be availlable.
If the active file is a program file then then dcal will flag an error if the necessary .obg files have not been added, (I was surprised that XBuilder created a dcx file from a module. My version of DCAL gives an error if you try to run dcl.exe on a module file).
Since there can only be one program file XBuilder should use this to control the project. A bit of thought on F1 Init and F2 Open. The programmer will need to use the compile option for both programs and modules. Creating new and open existing in both cases. So if the 'S3 *DCO_MGR' allowed the selection of .obj files and checks to see that the first file in the list is derived from a program file this would solve the problem.
Is it necessary to create an ini file for every program and module?
Compiling from within my preferred editor PSPad my version of dcal accepts
#INCLUDE 'dwtruss.inc' where dwtruss.inc is an include file in the program directory. The version used by XBuilder will not accept this. You have to place it in a sub-directory and use the relative path method.
Another surprise is the Module statement must not have a space before it. It apparently compiles from within XBuilder but no .obj file is created. I will have to research the versions of dcal.
I had placed XBuilder in a sub-directory of E:tempry but used source code in
E:\DCAL\DrwTruss. After a few 'experiments' XBuilder gave the message 'XBuilder has found itself inexplicably moved here E:Dcal\DrwTruss. OK to let XBuilder recover..'. This I accepted. Result another lot of duplicated sub-directories 'Xlab' and 'XStore'.
I did successfully compile and link.
More experimenting required
Regards
Rod Walker
Some thoughts on XBuilder.( Pietro Moras's Classic Dcal program editor).
The menu item 'S3 *DCO_MGR' should be placed before 'F6 Link'. Better still when the active file is a module file then the Link option should not be availlable.
If the active file is a program file then then dcal will flag an error if the necessary .obg files have not been added, (I was surprised that XBuilder created a dcx file from a module. My version of DCAL gives an error if you try to run dcl.exe on a module file).
Since there can only be one program file XBuilder should use this to control the project. A bit of thought on F1 Init and F2 Open. The programmer will need to use the compile option for both programs and modules. Creating new and open existing in both cases. So if the 'S3 *DCO_MGR' allowed the selection of .obj files and checks to see that the first file in the list is derived from a program file this would solve the problem.
Is it necessary to create an ini file for every program and module?
Compiling from within my preferred editor PSPad my version of dcal accepts
#INCLUDE 'dwtruss.inc' where dwtruss.inc is an include file in the program directory. The version used by XBuilder will not accept this. You have to place it in a sub-directory and use the relative path method.
Another surprise is the Module statement must not have a space before it. It apparently compiles from within XBuilder but no .obj file is created. I will have to research the versions of dcal.
I had placed XBuilder in a sub-directory of E:tempry but used source code in
E:\DCAL\DrwTruss. After a few 'experiments' XBuilder gave the message 'XBuilder has found itself inexplicably moved here E:Dcal\DrwTruss. OK to let XBuilder recover..'. This I accepted. Result another lot of duplicated sub-directories 'Xlab' and 'XStore'.
I did successfully compile and link.
More experimenting required
Regards
Rod Walker