Heh! You beat me to that point, Steve. :P ... I find that making no more than about three or four variables per dim is an excellent tradeoff for readability vs expandability. I find it especially true for common variable names, such as I frequently dim "i, j, bound, bound2 as integer, buffer, temp as string", because I almost always use those variables as those types.
It would be nice if REALbasic issued a warning or something for when a variable is not used, which you could disable via a pragma or something (such as "#pragma unused variablename", which would be similar to Visual Studio). And in any case, REALbasic should be optimized to simply not allocate space for unused variables on the stack (assuming that it doesn't do that already). On 7/21/06, Steve Garman <[EMAIL PROTECTED]> wrote:
> Now, why would they all even be dimmed in one line in VB? > To me it's just poor coding but I haven't used VB either. > Sure it looks efficient when one creates a single line Dim statement > but it really makes it harder when developing an application. > Dim i,j,k As Integer, s1,s2,s3 As String, etc. is neater and uses a > few less bytes but is it really worth it? And in VB, that would leave i, j, s1 and s2 all dimmed as Variant -- Steve Garman Using REALbasic 2006r2 Professional on Windows XP Pro _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
-- Keith Bennett, tA-Kane Software developer and Macintosh enthusiast Free iPods!!! http://www.freeiPods.com/?r=10867472 _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
