[dba-VB] Recent Discussion from MS on VB.Net and C# in VS 2010

Ooops, I meant 'at the end of each line for execution'.  I realize that
; is basically saying 'execute', which is what a CRLF in VB is doing
too.  In fact, you can also put multiple 'executable' lines in a single
line.  (At least you can in other languages that use ;, like
Javascript).

Though I do agree that syntax is to the language like women are to sex.
They're quirky, confusing, and will smack you down for the slightest
goof, but really, it's no fun without them.....

My question is something Max asked.  What is the real reason to change
then?  You've listed two that I understand (though I'm not really in
that world right now), available of learning resources, and client
requests.  Anything else?

Drew

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, March 16, 2010 10:35 AM
To: Discussion concerning Visual Basic and related programming issues.
Subject: Re: [dba-VB] Recent Discussion from MS on VB.Net and C# in VS
2010

 >You have to put ; at the end of each line

Not true.

Try to extend any syntactically valid line of code to one or more new
lines.  Break at any white 
space, as many times as you wish.

At the very end of the "last" line make sure that you have a ;

Compile.  It will compile and run.

 > Just my opinion though.  Not that I would never use C# or C++ because
of the ;, just find it 
annoying.

What I have discovered is that it helps to not "fight" any language,
just accept the syntax and move 
on.  There is waaaaaaay more important things in life than the ; at the
end of a line of code, or a 
code block designated by curly brackets.

I didn't invent the language (any of them), I am NEVER asked for my
opinion (on any of them).  Just 
accept the syntax of the language and move on.

John W. Colby
www.ColbyConsulting.com

The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.