Databases
StackOverflow2013
Postsdbo
POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
    primarykey
    data
    text
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMartín Canaval
    1. USwyred
    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. POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
      1. USElliott
      1. VTFavorite
    1. COProbably considered it more readable/understandable. If you were going to use constants, you'd probably want to at least express them in hex.
      singulars
      1. POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
      1. USJerry Coffin
    2. COWould *you* immediately recognise 201326592 as 192 Mi or 1073741824 as 1 Gi? It's impossible to tell at a glance how large those numbers are, or whether 201326592 is greater or smaller than 1073741824 - they just look random.
      singulars
      1. POIn Doom3's source code, why did they use bitshift to generate the number instead of hardcoding it?
      1. USmolbdnilo
 

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