4GL: size of pcode generated from function exceeds 32K limit. Error # -4451
Posted in 2005
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues
Can anyone help???? We are running informix 4GL version 7.3 on HP-UX and I received this message after I added some logic to an existing 4GL program and attempted to recompile it: -4451 The size of the pcode generated from this function has exceeded the 32K per function limit. The function will have to be simplified. Extract some portion of its code to a separate function, and call that function. Is the word "function" referring to the 4GL module or the function within the 4GL module? Is there any way to get around this without having to separate the code into a different function and/or module? This is a very large, complex program that is widely used and I would like to avoid making any significant changes to the structure of the program if possible. Please let me know if anyone has any info on this.
I had the Problem by myself. it is a single function, which is to large. You must divide this function in two function. (or even more) By the way, having this big function, may be, it's not good programming style. Try to do stepwise refinement, <kirstenkleist@pricechopper.com> schrieb im Newsbeitrag news:1116950870.404624.199180@g49g2000cwa.googlegroups.com... > Can anyone help???? > > We are running informix 4GL version 7.3 on HP-UX and I received this > message after I added some logic to an existing 4GL program and > attempted to recompile it: > > -4451 The size of the pcode generated from this function has exceeded > the 32K per function limit. > > The function will have to be simplified. Extract some portion of its > code to a separate function, and call that function. > > Is the word "function" referring to the 4GL module or the function > within the 4GL module? Is there any way to get around this without > having to separate the code into a different function and/or module? > This is a very large, complex program that is widely used and I would > like to avoid making any significant changes to the structure of the > program if possible. Please let me know if anyone has any info on this. >