Re: please revive project 4GL++, using 4gl for Windows and New Era
Posted in 2003
Topics: SQL Development & Query Writing, Connectivity: ESQL/C, 4GL & Embedded SQL, Java & JDBC Development
I believe the most important thing for the future of 4GL is that any compiler remain 100% backward compatible. If I have to go thru every line of code in every module looking for code that no-longer works, then the decision to move to another language is made for me. Rod sheppard rod@transmit.com.au ----- Original Message ----- From: "Andrej Falout" <afalout@xtra.co.nz> To: <informix-list@iiug.org> Sent: Tuesday, May 20, 2003 2:42 PM Subject: Re: please revive project 4GL++, using 4gl for Windows and New Era > In article <baaamu$ppe$1@terabinaries.xmission.com>, ferdez@moredata.pt says... > > > > Mark D. Stock wrote: > > > > > So as a matter of interest and debate, what's wrong with the attempts > > > made so far by the likes of 4Js and Querix? > > > > IMHO 4J's, Querix (and Aubit 4GL) have two problems: > > > > * They are not moving fast enough > > * They do not have the brand > > (Please note: my views may be slightly biased, as I actively participate in > Aubit project.) > > While probably true, one must note that for the size of the company, 4Js is > moving - not sure about slow or not, but FourJ's Genero is a significant > development, and therefore a challenge, if it get's released in this > millennium. You should take a look at Genero. > > Querix just released version 4, and while it's not a significant shift from > usual Querix mantra of "don't rock the boat", it's a progress, and a very > usable product. > > And speaking about Aubit, one nice, and at the same time not so nice, thing > about OpenSource products/projects is that they move as fast as they get > support from participating developers. So you can make it move faster, if you > help us. In my opinion, it will be much more realistic thing to do, then to > hope that IBM will listen to you. > > Speaking of witch, I'm very happy that IBM decided to do ANYTHING with Informix > 4GL - even if it's this rather strange EGL thingy. Actually, if they decided to > make EGL "Informix 4GL" compatible, I would like there approach very much. > Close to that goal would be to have Aubit compiler generate Java code instead C > or Perl code, as it does currently. Then again, I really don't have enough > information about I-4GL2EGL strategy to say even this much... > > So let me finish with an open invitation and a challenge, to all of you that > think that Informix-4GL can and should be more then it is - join the Aubit > Project, and you will get your chance to do something about it. > > -- > Yours, Andrej Falout, http://www.falout.com/disclaimer.html > Visit the OpenSource alternative, Aubit 4gl: http://aubit4gl.sourceforge.net > PLEASE NOTE: All HTML email sent to me WILL BE DELETED AUTOMATICALLY WITHOUT > READING. >
In message <bact7b$2fv$1@terabinaries.xmission.com>, Rodney Sheppard <rod@transmit.com.au> writes > >I believe the most important thing for the future of >4GL is that any compiler remain 100% backward compatible. > >If I have to go thru every line of code in every module looking for >code that no-longer works, then the decision to move to another language >is made for me. > Please forgive me if my out-of-date knowledge of I-4GL is about to show... We had (a very long time ago, I-4GL on DOS PCs) an application written in I-4GL that attempted to do 'intelligent' screen navigation, for example: Are the next 2 fields relevant? [] Dependant field 1 [] Dependant field 2 [] Next question [] and used lots of 'AFTER FIELD' and 'NEXT FIELD' (iirc) to navigate appropriately. When we tried to use 4GL-for-Windows, the users were able to point and click into the dependant fields irrespective of the answer to the preceding question. Had we moved at that time we would have had to re- validate all our entry screens. I guess the same situation would exist today. -- Andrew Lennard andy@kontron.demon.co.uk
"Rodney Sheppard" <rod@transmit.com.au> writes: > I believe the most important thing for the future of > 4GL is that any compiler remain 100% backward compatible. Noooo! IBM, please fix the "zero-length string is null" in 4GL so that it matches SQL's behavior. Don't keep this bug in the compiler forever!! -- Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412 Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142 President, CEO Fax: (760) 499-9152 My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B