Databases
StackOverflow2013
Postsdbo
POSwitch Statement Fallthrough...should it be allowed?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSwitch Statement Fallthrough...should it be allowed?
    primarykey
    data
    text
    <p>For as long as I can remember I have avoided using switch statement fallthrough. Actually, I can't remember it ever entering my consciousness as a possible way to do things as it was drilled into my head early on that it was nothing more than a bug in the switch statement. However, today I ran across some code that uses it by design, which got me immediately wondering what everyone in the community thinks about switch statement fallthrough.</p> <p>Is it something that a programming language should explicitly not allow (like C# does, though it supplies a workaround) or is it a feature of any language that is powerful enough to leave in the programmer's hands?</p> <p><strong>Edit:</strong> I wasn't specific enough to what I meant by fallthrough. I use this type a lot:</p> <pre class="lang-js prettyprint-override"><code> switch(m_loadAnimSubCt){ case 0: case 1: // Do something break; case 2: case 3: case 4: // Do something break; } </code></pre> <p>However, I'm concerned about something like this.</p> <pre class="lang-js prettyprint-override"><code> switch(m_loadAnimSubCt){ case 0: case 1: // Do something but fall through to the other cases // after doing it. case 2: case 3: case 4: // Do something else. break; } </code></pre> <p>This way whenever the case is 0, 1 it will do everything in the switch statement. I've seen this by design and I just don't know if I agree that switch statements should be used this way. I think the first code example is a very useful and safe. The second seems kind of dangerous.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdavidkonrad
    1. USFostah
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSwitch Statement Fallthrough...should it be allowed?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSwitch Statement Fallthrough...should it be allowed?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSwitch Statement Fallthrough...should it be allowed?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COdupe of http://stackoverflow.com/questions/174155/switch-statement-fallthrough-in-c?lq=1
      singulars
      1. POSwitch Statement Fallthrough...should it be allowed?
      1. USnawfal
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload