G
Guest
I'm building a Macro that is growing "like Topsy". At the moment it is 145
lines long, and will increase by about 50% from there when done. Because I'm
an old (really OLD<g>) VFP programmer, my thinking and development pattern is
shaped by that experience.
So, is it considered bad form to have a macro get large? I recall that in
C++ the recommendation was to try to hold a process to one screenful where
possible, and then build a "parent" process that called the segments in
sequence. However my macro consists of a series of nested For Loops that goes
five or six levels deep.
Just wondering -- and trying to learn <g>!
lines long, and will increase by about 50% from there when done. Because I'm
an old (really OLD<g>) VFP programmer, my thinking and development pattern is
shaped by that experience.
So, is it considered bad form to have a macro get large? I recall that in
C++ the recommendation was to try to hold a process to one screenful where
possible, and then build a "parent" process that called the segments in
sequence. However my macro consists of a series of nested For Loops that goes
five or six levels deep.
Just wondering -- and trying to learn <g>!