Linking object (written in C) with 4GL ver 7.32
Posted in 2009
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Internationalization & Character Sets
One of our clients trying to link with their 4GL ver 7.32, an old object code in C-routines. No source code available. With earlier versions of 4GL it worked smoothly. But with 4GL ver 7.32 it gives an error. This may due to the changes in calling C-functions. Because source code is not available including #include <fglsys.h> is not possible. Are there any workaround available ?
InformixSL wrote: > One of our clients trying to link with their 4GL ver 7.32, > an old object code in C-routines. No source code > available. > > With earlier versions of 4GL it worked smoothly. But with > 4GL ver 7.32 it gives an error. This may due to the changes > in calling C-functions. > > Because source code is not available including #include <fglsys.h> > is not possible. > > Are there any workaround available ? I've no idea really, but this looked relevant: http://www-01.ibm.com/support/docview.wss?uid=swg21108090 -- RGB
Without source code the only thing that the OPs client can do is to write wrapper functions to complete the mappings in fglsys.h to call the new interface functions when the original code calls the old interface functions. Write the wrapper functions and link them into the application. However, if the original intent of the lost source C code can be inferred, then I would just make the effort to rewrite them from scratch. Art Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, Sep 22, 2009 at 7:18 AM, RedGrittyBrick <RedGrittyBrick@spamweary.invalid> wrote: > > InformixSL wrote: > > One of our clients trying to link with their 4GL ver 7.32, > > an old object code in C-routines. No source code > > available. > > > > With earlier versions of 4GL it worked smoothly. But with > > 4GL ver 7.32 it gives an error. This may due to the changes > > in calling C-functions. > > > > Because source code is not available including #include <fglsys.h> > > is not possible. > > > > Are there any workaround available ? > > I've no idea really, but this looked relevant: > http://www-01.ibm.com/support/docview.wss?uid=swg21108090 > > -- > RGB > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >
On Tue, Sep 22, 2009 at 03:19, InformixSL <informixsl@gmail.com> wrote: > One of our clients trying to link with their 4GL ver 7.32, > an old object code in C-routines. No source code > available. > > With earlier versions of 4GL it worked smoothly. But with > 4GL ver 7.32 it gives an error. This may due to the changes > in calling C-functions. > > Because source code is not available including #include <fglsys.h> > is not possible. > > Are there any workaround available ? Exactly which sub-version of I4GL 7.32 have you got. I4GL 7.32.xC2 does not have the fix in place; AFAIK, 7.32.xC3 or 7.32.xC4 does. The 'fix' is to provide cover functions - as already intimated. And you are living dangerously running the programs without the source code. You need to reimplement the code for which you don't have the source - you are not safe until you have done so. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2008.0513 -- http://dbi.perl.org/ "Blessed are we who can laugh at ourselves, for we shall never cease to be amused." NB: Please do not use this email for correspondence. I don't necessarily read it every week, even. Pablo Picasso<http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html> - "Computers are useless. They can only give you answers."