Procedures cut exe size?

[netmaestro]

I had an interesting thing happen today. I have a program that is around 400 lines with a datasection containing about 30k or so of graphics. The structure of the program was all inline code with If-ElseIf-ElseIf-ElseIf-Endif to choose which code to run based on the mode found in the program parameters. It compiled to around 147k for the exe size. Once I was happy with the way the code ran, I restructured the program so that each of the code sections was in its own procedure and all the If-ElseIf block did was choose which procedure to run and then end. The code itself changed very little, nothing significant was removed. But after the restructure, the compiled exe size went down to 115k from 147.

Has anyone else noticed similar? And if this is something to be expected, can someone shed some light on why? I'm flummoxed as to why this would be.

[MachineCode]

Without seeing the code, it sounds like the procedures are replacing many repetitions of (small?) blocks of code, and therefore obviously the executable would become smaller. But only you know if that's the case, since you can see the code.

[netmaestro]

No, the blocks only execute once. There's loops in them but the loops are in the procs too.

[J. Baker]

That's interesting. I'll have to do my own test sometime and see what results I get. I usually use procedures anyway. But if what you are saying works for all code, then that could be helpful.