Ok - to settle this age old issue once for all.... :) http://www.realsoftware.com/feedback/viewreport.php?reportid=umcympop
in order to get the best performance, it is common to use: dim U as integer = myArray.UBound for i as integer to U .. Next instead of: for i as integer to myArray.UBound .. Next ( which is much cleaner ) It would be helpful if there were NO performance penalty in using the latter syntax. If the compiler could just refer to the internal array size count directly without any function call overhead, we would get this, and I could use the latter syntax "performance guilt free" :) (This assumes of course that INTERNALLY RB maintains such a variable that gets updated whenever elements are added/removed) Sign on here: http://www.realsoftware.com/feedback/viewreport.php?reportid=umcympop _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
