This is just beautiful!
-
If txtProvCt.Text = txtProvCtS Then Else giUpdate = True End If
-
If txtProvCt.Text = txtProvCtS Then Else giUpdate = True End If
-
and not unusual... :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
CPallini wrote:
and not unusual...
Queue the Tom Jones soundtrack.
Deja View - the feeling that you've seen this post before.
-
If txtProvCt.Text = txtProvCtS Then Else giUpdate = True End If
-
If txtProvCt.Text = txtProvCtS Then Else giUpdate = True End If
-
If txtProvCt.Text = txtProvCtS Then Else giUpdate = True End If
It's one of my coding rules, which is really useful once you get the point :
if(NULL != l_poStrTest)
{ // Format error message
l_poStrTest->Format
( "My code : %d"
, l_nErrorCode
);
}
else
{ // Error code
}It's also all about defines :
#define MY_TEST
#ifndef MY_TEST
int l_nSize = GetStringSize(l_poStrText);
#else // MY_TEST
// int l_nSize = TempoFunc(l_poStrText);
#endif // MY_TESTBy doing so, I write the full structure of the code which is then ready to fill up, and it also helps to keep an eye-track of the execution logic (inequal statement first) so that you don't have to know if the test is about inequality (!= or #ifndef) or equality (== or #ifdef). You just have to spot the upper or lower block of code and see if it is defined/filled or not... This also force to structure carefully your code and put some air between the lines, instead to write a rock-compact block of code... Kochise PS : I often write empty equality code like this
if(NULL != l_poStrTest)
{ // Format error message
l_poStrTest->Format
( "My code : %d"
, l_nErrorCode
);
}
else{} // Error code, ready to be unrolled and filled with error handling codeIn Code we trust !
-
If txtProvCt.Text = txtProvCtS Then Else giUpdate = True End If
= is more faster than !=..thats why:):-D
Regards, Sylvester G sylvester_g_m@yahoo.com