50 thousand line does not large in a medium-size program
Speak for yourself 
Leaving aside for the moment consideration of whether the size of the procedure is the actual cause of the problem.
I've seen similarly-sized "flat code" generated by macro-based programming systems, usually in what would now be called "retrocomputing" contexts. The result was typically processed by a FORTRAN compiler, but gave anything else problems.
I've similarly seen programming systems where each line of (what appeared to be) high-level code was processed in a way in which resulted in an intermediate representation which would later be stuffed into memory, rather like a specialist assembler.
I can accept that something behaving as a specialist assembler might emit an intermediate representation which wasn't amenable to being broken up into procedures. In any other context, doctrine would have it that 50kloc for a procedure is grossly excessive.
I suggest trying something like changing
program frbl;
procedure guiyg;
var
...
begin
line1;
...
line50k
end;
begin
guiyg
end.
into
program frbl;
procedure guiyg;
var
...
procedure guiyg1;
begin
line1;
...
end;
procedure guiyg1000;
begin
line1000;
...
end;
...
begin
guiyg1;
guiyg1000;
...
end;
begin
guiyg
end.
That obviously has excessive use of up-scope variable access, but should work (subject to to any comments from Marco et al.) if the problem is /solely/ procedure size. That's not to say that it's particularly good style.
MarkMLl
Recent
