"Michael Mayer [C# MVP]" <mike@mag37.com> wrote in message
news:O5jmXK0HEHA.3376@TK2MSFTNGP09.phx.gbl...
> You can always do this in your vb code:
>
> If x > 10 Then
> x = x * 15 ';
> End If
>
> ;-)
>
>
> mike
>
>
> "Al Manint" <al_manint@nospam.yahoo.com> wrote in message
> news:OY3v$8zFEHA.1156@TK2MSFTNGP12.phx.gbl...
> > The main reason I think this is a bad idea is how you read code...
> >
> > A semicolon is a statement terminator. In VB, the end of line is the
> > statement terminator unless you use a _ to continue to the next line.
> >
> > I'm not saying you can't do it but I just think that it would make the
> code
> > harder to read...
> >
> > Al Manint, MCSD (VB 6 ugh), MCSD.NET (C# MUCH BETTER - uses semicolons
> :)),
> > MCDBA
> >
> > (now you know how I sit on this issue: I like semicolons - I just don't
> > want to have to describe why I have all these semicolons in my vb code
if
> > they are unnecessary.)
> >
> > "Andrew Baker" <no@spam.com> wrote in message
> > news:ebl16LrFEHA.3568@tk2msftngp13.phx.gbl...
> > > One of by biggest hassels in the past jumping from C++ to VB and back
> was
> > > the forgetting or adding a semicolon at the end of a statement. (the
> > other
> > > was bracketing method calls in VB, but that is now fixed).
> > >
> > > Why didnt Microsoft allow for the optional use of semicolons in VB, so
> the
> > > code would be much closer? The compiler would just ignore it anyway.
> > >
> > > Another is the difference between new and New. at least VB.Net
changes
> > > new -> New for me, but I would have thought it would have been better
to
> > > keep the same in both languages (particularly as VB.Net changes the
> > > capitalisation for us anyway)
> > >
> > > I know the syntax checking picks these up, but it is just my gripe for
> the
> > > day.
> > >
> > > Andrew
> > >
> > >
> >
> >
>
>