>>Hi Martina,
>>
>>What is the "WITH .RETURN.. ENDWITH bug"???
>
>IIRC, it's that you should not just jump out of a with/endwith block - so no return, loop or exit statements, because with/endwith seems to stay in effect, having not reached the endwith statement. So the "with stack" (for lack of better term) remains in unresolved, or active, state, is not automatically reset. Don't remember what ill effects it may have, but I do remember that I went through all of my code when it was discovered and checked for this. Found a couple.
Thanks for this info, Dragan.
Our software has a lot of places with such code. I have never noticed any negative effects.
Is there any search-word I can use to find additional info? Does anyone else know more details?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
