Re: I4gl C compiler

In article <dhyman.1.0056D03E@jjma.com>, dhyman@jjma.com writes: <TEXT LOST BY America On-Line - Sorry they just don't understand > Tim Schaefer writes: Dave, SCO has a C compiler that will work just fine. You should consider using MAKE files and splitting up your program into modules similar to C programming. Put your GLOBALS into a globals file, and try to keep your functions one to a source file, unless of course they are small functions, then bunch 'em up. You can set up your own libraries this way, so nobody will pound you for not being object orientated. :) For example, program.4gl - Main program with MENU and MAIN code block program01.4gl - GLOBALS file. Put GLOBALS "program01.4gl" in all your other program modules. program02.4gl - Initialization and buffer management routines. program03.4gl - Some function. program04.4gl - Another function program05.4gl - Yet another function and so on My personal opinion is that the I4GL environment is a pain in the neck and actually slows you down. The planned compile portion is a REAL time waster. I4GL is a nice feature for novice programmers, the nice part is that it handholds you through a compile, and then takes you to the .err file when you bomb out. But using MAKE is much more productive, and not confined to the agony of the I4GL menu and interface. I create a makefile, like program.mk, and make the program " make -f program.mk". If the program errors out, I VI the .err file, and BTW, there's a vi-the-error-file script on the freeware site at emory.edu. This way you don't correct the err file only to discover at compile time the changes were to the wrong file. If you or anyone is interested, I have a makefile with the rules to get you from 4GL to EXE. Best wishes for you in 4GL programming. Tim Schaefer The Computer Business Co. -- No animals used in my programs are harmed in any way!