Re: How to do "continue" in VB?

From: lonnyw (<)
Date: 02/06/05 

Date: Sun, 6 Feb 2005 22:14:16 -0000

> Quote from Bruce McKinney(Hardcore Visual Basic, Second Edition, ch#1)
> ---
> <QUOTE>
> "One minor hole in the Visual Basic looping structure is the lack of a
> Continue statement. Other languages offer a way to jump from the middle
> of a loop to continue with the next iteration. Basic only lets you jump
> completely out of the loop. You can work around this annoying limitation
> with Goto, but you shouldn't have to."
> </QUOTE>
> ---
>
> can't see your loop, so can't give you other ideas...
> (you should be able to find this book at your MSDN)

Goto will be fine, thanks!!

Relevant Pages

  • Re: goto in php
    ... loop, so unless you break, it does nothing at all... ... // Will 'goto' the first 'do'... ... Notice that 'break n' will basicly count backwards, (not which one to jump ... > sentence skipping some code if it's positive - "go-to" a lower part in the ...
    (alt.php)
  • Re: how do people feel about exit function from loop
    ... A for loop is very clear. ... exit conditions for the loop (assuming that someone isn't using an Exit ... Because goto can jump into loops and jump all over the place. ...
    (microsoft.public.vb.general.discussion)
  • Re: How to do "continue" in VB?
    ... Quote from Bruce McKinney ... "One minor hole in the Visual Basic looping structure is the lack of a ... Other languages offer a way to jump from the middle ... of a loop to continue with the next iteration. ...
    (microsoft.public.vb.general.discussion)
  • Re: Why is GOTO bad?
    ... BREAK label or BREAK n is more flexible working with _ALL_ types of loop. ... "GOTO label"? ... With break label you can't accidentally jump inside ...
    (microsoft.public.vb.general.discussion)
  • RE: for next loop problems
    ... The recommended way to jump out of a for/next loop is to use the Exit For ... statement i.e instead of GoTo 178 use Exit For: ... Don't use absolute branching (GoTo 178): this style of coding is a nightmare ...
    (microsoft.public.excel.programming)