Re: strange behaviour of .skip command [message #60373 is a reply to message #60371] |
Thu, 15 May 2008 06:21   |
pgrigis
Messages: 436 Registered: September 2007
|
Senior Member |
|
|
Manodeep Sinha wrote:
> Hello everyone,
>
> In the fine tradition of *trying* to get things done quick, I have a
> code segment that looks like :
>
> if {some condition} then begin
> .
> .
> {some random text to make the code break}
>
> endif else begin
> .
> .
> endelse
>
> The code breaks at the random text, I check for the variables and
> conditions that were set in the "if part", and if all is well, I issue
> a .skip and a .continue. Now, it turns out that under such conditions
> (if the random text is located right before the endif statement), the
> code execution actually proceeds through the else-endelse segment as
> well. However, if there is any other statement between the random text
> and the endif statement, then the code execution does not go into the
> else-endelse segment.
Simply put a "stop" instead of your random test, and resume execution
with .continue.
Then there is no need to use .skip.
Cheers,
Paolo
>
> Granted this is quite an unique situation to find oneself in, but
> having spent the better part of a day trying to track this down, I
> thought I would check with the group and see if this was a
> reproducible behaviour.
>
> Is my understanding of .skip incorrect ? Does it skip through more
> than 1 line even when invoked without an additional parameter ?
>
> In any case, it boggles my mind seeing code go through both the "if"
> and "else" part in one execution !
>
> Cheers,
> Manodeep
|
|
|