And how they work …..<\/p>\n\n\n\n
In a bug report I made I posted a tiny sample of code<\/p>\n\n\n\n
Dim tokens() As String\n\nSelect Case True\n \nCase tokens.ubound < 0\n \nCase tokens(0) = \"End\"\n \nCase \"Dim\"\n break\n \nEnd Select\n<\/code><\/pre>\n\n\n\n(Not this code has a known bug in it – Case “Dim” is wrong but it illustrated the bug I was reporting) I’ve used this style for very long sections of code esp where I dont want to clutter it up with extraneous “if then” or “elseif”<\/p>\n\n\n\n
But it gathered a curious comment that convinced me the writer of that comment isnt certain how SELECT CASE works. The comment was <\/p>\n\n\n\n
I see no sense in the line \u201eSelect Case True\u201c, since True is always True. So the error message points in the right direction, correcting this line.<\/p><\/blockquote>\n\n\n\n
While I understand the reasoning it also happens to illustrate the misunderstanding of how select case works.<\/p>\n\n\n\n
The statement that follows select case<\/em> is known as the Test Expression<\/em>.<\/p>\n\n\n\nXojo will then evaluate each case expression and find the first one that matches that Test Expression.<\/p>\n\n\n\n
In the case of the code above it will find the first one that has a case expression that is true<\/p>\n\n\n\n
It behaves as if the code was written as <\/p>\n\n\n\n
if true = (tokens.ubound < 0) then\n \nelseif true (tokens(0) = \"End\") then\n \nelseif true = ( \"Dim\" ) then\n\nend<\/code><\/pre>\n\n\n\nThis sample replicates the same bug as the original BUT this time the compiler correctly complains about the comparison between TRUE and “DIM” (which is what my bug report was about originally)<\/p>\n\n\n\n
Select case can be a very handy way to declutter code and remove a lot of “if then” and “elseif then” from your code.<\/p>\n\n\n\n
But only if you know how it works.<\/p>\n","protected":false},"excerpt":{"rendered":"
And how they work ….. In a bug report I made I posted a tiny sample of code (Not this code has a known bug in it – Case “Dim” is wrong but it illustrated the bug I was reporting) I’ve used this style for very long sections of code esp where I dont want … <\/p>\n