Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The difference is that <code>const char *</code> is a pointer to a <code>const char</code>, while <code>char * const</code> is a constant pointer to a <code>char</code>. </p> <p>The first, the value being pointed to can't be changed but the pointer can be. The second, the value being pointed at can change but the pointer can't (similar to a reference).</p> <p>There is also a</p> <pre><code>const char * const </code></pre> <p>which is a constant pointer to a constant char (so nothing about it can be changed).</p> <p>Note:</p> <p>The following two forms are equivalent:</p> <pre><code>const char * </code></pre> <p>and</p> <pre><code>char const * </code></pre> <p>The exact reason for this is described in the C++ standard, but it's important to note and avoid the confusion. I know several coding standards that prefer:</p> <pre><code>char const </code></pre> <p>over</p> <pre><code>const char </code></pre> <p>(with or without pointer) so that the placement of the <code>const</code> element is the same as with a pointer <code>const</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the difference between char * const and const char *?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USworkmad3
    1. USworkmad3
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is the difference between char * const and const char *?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWould it be worthwhile to note what happens if multiple variables are specified in the same declaration? I believe `const int *foo,*bar;` would declare both `foo` and `bar` to be `int const *`, but `int const *foo, *bar` would declare `foo` to be a `int const *` and `bar` to be `int *`. I think `typedef int * intptr; const intptr foo,bar;` would declare both variables to be `int * const`; I don't know any way to use a combined declaration to create two variables of that type without a typedef.
      singulars
      1. PO
      1. USsupercat
    2. CO@supercat `I believe const int *foo,*bar; would declare both foo and bar to be int const *`: Yes. `but int const *foo, *bar would declare foo to be a int const * and bar to be int *`: _No!_ It would be exactly the same as the previous case. (See http://ideone.com/RsaB7n where you get the same error for both foo and bar). `I think typedef int * intptr; const intptr foo,bar; would declare both variables to be int * const`: Yes. `I don't know any way to use a combined declaration to create two variables of that type without a typedef`: Well, `int *const foo, *const bar;`. C declarator syntax...
      singulars
      1. PO
      1. USgx_
    3. CO@gx_: So I was wrong--my uncertainty was why I suggested that it might be helpful to say what the rules are. What would `int const *foo, *volatile bar` do to `bar`? Make it both `const` and `volatile`? I miss Pascal's clean separation of declared-variable names and their types (a pointer to an array of pointers to integers would be `var foo: ^Array[3..4] of ^Integer`;`. That'd be some funny nested parenthesized thing in C, I think.
      singulars
      1. PO
      1. USsupercat
 

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