Re: Suggested Changes to 4gl

In article <1992Dec16.213256.21452@nezsdc.icl.co.nz> you write: : John Oliver writes... : >How about dynamic use of I4GL call command, i.e be able to issue:- : > call func_name : >where func_name is a char variable storing the name of a function. I think we have this (sort of.) See pages S-198 -> S-212 of the 4.1 4GL supplement. We provide a fgl_call(char *funcname, int nparams) macro which turns into: p4gl_call("funcname", nparams) - 4gl-rds or simply, funcname(nparams) - w/c4gl So, using a very short C function with 4gl-rds, you can call functions "by name." In C-4gl, the only method to do this would be to create a lookup table of strings and function pointers. : >Under the current I4GL, this is impossible. The best you can do us use the run : >command to run named stand alone executables, but this leaves a whole : >lot of sleeping parent processes around when leaves of complex menu trees : >are reached. Or, in 4gl-rds, you can load individual pcode files dynamically and execute them (see the fgl_start() function, page S-207.) : >------------------------------------------------------------------------ : > John Oliver, Ernst & Young Management Sciences, Auckland, NEW ZEALAND : Hugh Grierson Fujitsu/ICL New Zealand - Software Development Centre Girard Chandler (Informix 4GL Development)