Thread: Visual Basic
View Single Post
  #12   Spotlight this post!  
Unread 13-11-2007, 23:43
jee7s jee7s is offline
Texan FIRSTer, ex-frc2789, ex-frc41
AKA: Jeffrey Erickson
FRC #6357
 
Join Date: Nov 2007
Rookie Year: 1997
Location: Dripping Springs, TX
Posts: 315
jee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond reputejee7s has a reputation beyond repute
Re: Visual Basic

I really meant my fall through explanation to be focused on C/C++. Frankly, I have never used it in a C# application, but I assumed the C-style syntax would support it...I was apparently wrong.

So, let's apply my previous post to C/C++ only.

Also, the link you posted is a good work around for a fall through. However, as a practice, GOTO statements violate OOP principals, and I try to avoid them at all costs.

P.S....I've been itching for a correlary to __asm (from C++) in C#. Perrhaps __cpp, or __C++, or __cplusplus to allow for inline C++ code in C#. I suppose I'll never see it.