chaat
Sophomore Member
Posts: 59
|
Post by chaat on Jul 24, 2013 16:34:19 GMT -5
I've been using SPF/SE for a long number of years and I'm in the process of attempting to test SPF-Lite to see if it has the functionality of SPF/SE.
One of my KEYS is mapped to the following command which saves the current file being edited and then invokes my compiler with a fairly long argument string.
save; system nostop COB2 -c -q"NOSEQ MAP NOTERM XREF(FULL) NOEXIT NOADATA NOCOMPILE BINARY(S390) CHAR(EBCDIC) FLOAT(HEX) NOPROBE NOFLAGSTD SIZE(16000K)" -IF:\SPFSE\LIB -IF:\SPFSE\WORK &zdsn
Notice that in the above string the variable &zdsn is actually substituted with the name of the current file being edited when the command is executed..
can someone show me how to do this with SPF-Lite ?
Thanks
Chuck H.
|
|
|
Post by George on Jul 30, 2013 14:51:27 GMT -5
Chuck: Robert: Have a look in the \MACROS folder distributed with 7.0. In there you will find a PB.MACRO file which I use to run PowerBasic compiles from the edit session.
It saves the file, and then runs the compile. If a compiler error is reported, it opens and reads the compiler log file, extracts the line/column where the error is reported and then positions the edit display to that line, displaying the compiler error message at the top of the screen.
It uses a small BAT file to run the compiler, mainly to simplify the building of the command string, which, as your example shows, can become quite long. The sample macro doesn't show the BAT file, but it consists simply of:
CD %1 "C:\Program Files (x86)\PBWin103\Bin\PBWin.exe" /L /Q /I"C:\Program Files (x86)\PBWin103\WinApi\" %2
It of course is not exactly what you need, but it has all the pieces you need to tweak this for your own compiler. Certainly worth a look.
George
|
|