Databases
StackOverflow2013
Postsdbo
POC Options Good Style?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POC Options Good Style?
    primarykey
    data
    text
    <p>I am new to C, and am having some fun playing around with bitwise operations. What I am doing seems to work, I am just wondering if it is considered good style.</p> <p>Alright so let's say my program has 3 command-line options, <code>-a</code>, <code>-b</code>, and <code>-c</code>. Previously I would have had 3 ints act as booleans, say <code>aFlag</code>, <code>bFlag</code>, and <code>cFlag</code>. Then when I call my <code>processOpts( int *aFlag, int *bFlag, int *cFlag)</code> function, I would pass <code>&amp;aFlag</code>, <code>&amp;bFlag</code>, and <code>&amp;cFlag</code> as arguments, and set them like <code>*aFlag = 1</code>.</p> <p>Here's my new approach: have 1 <code>int *options</code> to represent all of the options, and treat it like an array of booleans. So to set them in the function:</p> <pre><code>case 'a': *options |= 1; break; case 'b': *options |= 2; break; case 'c': *options |= 4; break; </code></pre> <p>Then, back in <code>main</code> (or wherever), when I want to test to see if an option is chosen:</p> <pre><code>if ( *options &amp; 1 ) // Option 'a' selected if ( *options &amp; 2 ) // Option 'b' selected if ( *options &amp; 4 ) // Option 'c' selected </code></pre> <p>My question is: which method is considered better style? The first way could be more clear and less error-prone, whereas the second would probably make for easier refactoring (no need to change function prototype, as it's just one <code>int</code>).</p> <p>Or, is there an even better way to do this? <code>:D</code></p> <p>EDIT: added breaks per Mat's suggestion.</p> <p>Thanks for all the responses, I am quite impressed with this community and its willingness to help everybody learn—you guys rock!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFred
    1. USFred
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. POC Options Good Style?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POC Options Good Style?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COdon't forget to `break` between your `case`s
      singulars
      1. POC Options Good Style?
      1. USMat
    2. COCan you do bit fields in raw c? struct someStruct { int flaga:1; int flagb:1}; etc? (I've pretty much always used c++ compilers)
      singulars
      1. POC Options Good Style?
      1. USforsvarir
    3. CO@forsvarir: Bit fields are a c construct. I think c++ inherited them without change.
      singulars
      1. POC Options Good Style?
      1. USdmckee
 

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