Re: 4GL: Turn off cursor name mangling.

In article <33289d4c.51742932@gate.idg.no>, Nils Myklebust <Nils.Myklebust@idg.no> writes >:In article <3327f236.7944814@gate.idg.no>, Nils Myklebust >:<Nils.Myklebust@idg.no> writes >...snip... >:>We use the -globcurs option to c4gl which is definitely documented. >...snip... >:>Jacob Salomon <jake@apparel.net> wrote: >:>: let scratch >:>: = "update gplibdoc", >:>: " set long_desc = ?", >:>: " where current of lock_lib_desc_curs" > >David Williams <djw@smooth1.demon.co.uk> wrote: > >: Where to >: "where current of ",CURSOR_NAME(lib_desc_curs) > >Why would you want to use this function instead of simply using the >-globcurs parameter? In my case we have >200 programs and a makefile which uses a script to compile each program when required. The makefile is handled by my manager who does not want to change it for just my one program. especially as this is a product (15 sites - we have just added an OWS site in Scotland). I assume that this is similar to rowids (-globcus may I suspect be removed in a future release, we heard nothing about not using rowids in v2, mumblings in 4.o and a definate stop using now in 4.1 now in v7 engines you cannot always using them easliy). I imagine that Informix want to get people to move towards unique cursor names in each binary you compile and -globcurs is a hold over feature until SAP/other big products move to not needing -globcurs. Informix are rationalising how RDS/C4GL compile and this is a part of that rationalisation. >With this function you may still run into the problems with the >mangling algorithm sometimes creating the same name for different >cursors. >Of course it is a solution if you have the same cursor names in >different modules. But you don't do that, do you? :-) > > >Nils.Myklebust@idg.no >NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway >My opinions are those of my company >The Informix FAQ is at http://www.iiug.org -- David Williams