In this particular program, I will be rearranging the blocks of code into different orders, and it's easiest to read the logic of the program top down.
If I used subroutines, In order to keep that top down logic, every time I move a subroutine reference in the main code to a new location, I'd also have to move the subroutine code around also so if you were to read the program, it still flow top down, and your not hunting out where each subroutine is. I use the small main with subroutines often. But in this case, readability is the key. None of the other methods are wrong, just in this instance, I'd prefer not to use them. George > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- > boun...@listserver.u2ug.org] On Behalf Of Steve Romanow > Sent: Monday, February 07, 2011 4:24 PM > To: U2 Users List > Subject: Re: [U2] Does UV have a "BLOCK" command > > On 2/7/2011 4:20 PM, George Gallen wrote: > > My main aversion to the subroutine method is that to me, I think > > of subroutines as code that used in multiple places, if it's only > > used once, why not put in the main code. > > > > Yes, it can be used once....and still be a subroutine... > > > > George > > /listserver.u2ug.org/mailman/listinfo/u2-users > I like to use subroutines as a way to shorten my main loop into a nice > concise routine. > If there is a good logical chunk, why not take it. Even if it is only > used once. Something like GET.UPC or HANDLE.KIT > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
