Salakhetdinov Shamil
mcp2004 at mail.ru
Thu Jul 4 06:10:21 CDT 2013
Hi Stuart -- I'm sorry if my note on "code clearness being dependent on many factors" wasn't accepted there as it was intended to: that wasn't critique of 185 lines long of VBA code - I do realize that 185 codes lines sequence in VBA will execute (much) quicker than 15+ functions/subs especially if that subs/functions will be called in long running cycle(s). As for modern dev tools the news are good here - they do use different compilation optimization techniques ( http://en.wikipedia.org/wiki/Optimizing_compiler ) as e.g. inline functions' ( http://en.wikipedia.org/wiki/Inline_function ) compilation time inline expansion ( http://en.wikipedia.org/wiki/Inline_expansion ), which I meant and which is " enabling transformation for other optimization s ( http://en.wikipedia.org/wiki/Optimization_(computer_science) )... Hope VBA will get something like that in the future. Once again I'm sorry to hear my note was accepted as criticism there - it wasn't my intention. I must also note I typed my prev.posting from my WinPhone - so it was short and it was not clear enough AFAIS. I will try to make my posting more detailed in the future. Thank you. -- Shamil Thursday, July 4, 2013 8:43 PM +10:00 from "Stuart McLachlan" <stuart at lexacorp.com.pg>: >Bad news on modern dev tools as VS 15+ sub-routines would still exevcute slower than 185 >code lines long "clean code sequence". > >There will ALWAYS be overhead in calling sub routines because of the requirement to >write/read stack pointers. Even more so in a framework such as VB compared to native >code. > >-- >Stuart > >On 4 Jul 2013 at 13:22, Salakhetdinov Shamil wrote: > >> >>> Followed by 185 lines of code. >>> Good news on modern dev tools as >> VS is that they optimize subroutines calls and so having 185 code >> lines long "clean code sequence" would execute as fast as 15+ >> subroutines representing the same logic. Hope VBA will get such >> compilation and execution features in the future versions. I have >> quoted "clean code sequence" just to note that "code clearness" is >> dependent IMO on many factors. >> >> -- Shamil >> Wednesday, July 3, 2013 10:15 PM -07:00 from "Rocky Smolin" < rockysmolin at bchacc.com >: >> > Figuring out how to write a module without the use of GoTo is fun, a bit >> > challenging in some cases, and 'more elegant' as you say. >> > >> > I use GoTo because it produces a nice clear sequence. For example: If >> > condition true, then followed by 185 lines of code, followed by end if so >> > you have to go all the way to the end of the 185 lines to find out what >> > happens of the condition is false. >> > >> > As opposed to If condition False then GoTo ExitModule: >> > >> > Followed by 185 lines of code. >> > >> > Rocky >> > >> > <<< skipped >>