Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is probably wrong in esoterical ways, but, to make it simple:</p> <p>Value types are values that are passed normally "by value" (so copying them). Reference types are passed "by reference" (so giving a pointer to the original value). There isn't any guarantee by the .NET ECMA standard of where these "things" are saved. You could build an implementation of .NET that is stackless, or one that is heapless (the second would be very complex, but you probably could, using fibers and many stacks)</p> <p>Structs are value type (int, bool... are structs, or at least are simulated as...), classes are reference type.</p> <p>Value types descend from System.ValueType. Reference type descend from System.Object.</p> <p>Now.. In the end you have Value Type, "referenced objects" and references (in C++ they would be called pointers to objects. In .NET they are opaque. We don't know what they are. From our point of view they are "handles" to the object). These lasts are similar to Value Types (they are passed by copy). So an object is composed by the object (a reference type) and zero or more references to it (that are similar to value types). When there are zero references the GC will probably collect it.</p> <p>In general (in the "default" implementation of .NET), Value type can go on the stack (if they are local fields) or on the heap (if they are fields of a class, if they are variables in an iterator function, if they are variables referenced by a closure, if they are variable in an async function (using the newer Async CTP)...). Referenced value can only go to the heap. References use the same rules as Value types.</p> <p>In the cases of Value Type that go on the heap because they are in an iterator function, an async function, or are referenced by a closure, if you watch the compiled file you'll see that the compiler created a class to put these variables, and the class is built when you call the function.</p> <p>Now, I don't know how to write long things, and I have better things to do in my life. If you want a "precise" "academic" "correct" version, read THIS:</p> <p><a href="http://blogs.msdn.com/b/ericlippert/archive/2010/09/30/the-truth-about-value-types.aspx" rel="nofollow">http://blogs.msdn.com/b/ericlippert/archive/2010/09/30/the-truth-about-value-types.aspx</a></p> <p>It's 15 minutes I'm looking for it! It's better than the msdn versions, because it's a condensed "ready to use" article.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the difference between a reference type and value type in c#?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USxanatos
    1. USxanatos
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt's wrong in more than esoteric ways. It's *fundamentally* wrong I'd say - because reference type values are still passed by value as well; it's just that the value is a reference, not an object. See http://pobox.com/~skeet/csharp/parameters.html. Oh, and local variables can end up on the heap too, for example if they're captured or part of an iterator block.
      singulars
      1. PO
      1. USJon Skeet
    2. COIterators blocks are converted to classes, so "behind you" they are "fields of a class". Same for closures. Yeah... I forgot to write the distinction between the "pointer" (the reference) and the "pointed"
      singulars
      1. PO
      1. USxanatos
    3. CO@xanatos: Sure, they're fields of a class after compilation - but they're still local variables in the source code. I also wouldn't call the references themselves "value types" - I think I know where you're coming from, but I don't think it's a good idea to muddy the waters in this way.
      singulars
      1. PO
      1. USJon Skeet
 

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