RE: D4GL vs. I4GL

I-4GL and D-4GL will happily coexist on the same machine - indeed on our development box we compile the same source code with the 2 compilers and develop in parrallel. Straight recompilation is fairly unproblematic. The major problems we hit were because the D4GL compiler is much stricter than the I-4GL compiler and makes checks that I4GL does not at link time - e.g. consistent definition of globals variables and the number of parameters. There are also a few niggling bugs - ( they could however have been fixed in the 2.10 release - I have not checked yet. However they are all minor syntactical changes and all could be worked around. Beyond the straight compile the amount of work required depends on the nature of your code. For instance if you use a lot of before and after field validation you will not be able to click anywhere in the GUI version as all the validation will either need to be tripped or disabled totally. You also need to take an opinion as to how backwardsly compatible you would like the code to be. The whizzier GUI functionality breaks your compatibility with I-4GL. That said you can do impressive things with a little careful coding that are I-4gl compatible. I would certainly recommend that you evaluate it. > -----Original Message----- > From: Stefanie Vario [SMTP:svario@speedlink.net] > Sent: 21 January 1999 05:38 > To: informix-list@iiug.org > Subject: D4GL vs. I4GL > > We're looking into installing D4GL and converting some of our 4GL > applications to D4GL. Has anyone done this before? If so, what types > of problems/issues did you come across? Was it just a simple recompile > of your existing 4GL applications into D4GL or did you actually have to > make changes to the code? We would also like to keep some of our > existing 4GL applications alone. Can D4GL and 4GL co-exist together on > the same machine? > > Any info from anyone who has gone through this would be appreciated. > Thank you > > Stefanie Vario > svario@roushind.com