Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>So my question: What's going on here, and why? (Also, how can both of those answers be correct...?)</p> </blockquote> <p>I actually think the answer to <a href="https://stackoverflow.com/questions/11433943/why-does-objective-c-block-still-work-without-copying-it-to-the-heap">the other question</a> is wrong, in that it doesn't answer that particular question about blocks in ARC. The question is about passing a stack based block from one function/method to another. The answer is about something different, which is capturing __block variables within a block. That's a different issue.</p> <p>The answer to your question is in the FAQ of the <a href="http://developer.apple.com/library/ios/#releasenotes/ObjectiveC/RN-TransitioningToARC/Introduction/Introduction.html" rel="nofollow noreferrer">Transitioning to ARC Release Notes:</a></p> <blockquote> <p>Blocks “just work” when you pass blocks up the stack in ARC mode, such as in a return. You don’t have to call Block Copy any more. You still need to use [^{} copy] when passing “down” the stack into arrayWithObjects: and other methods that do a retain.</p> </blockquote> <p>So the way this works is that when you pass a block (in your case a block literal allocated on the stack), the compiler <strong>does not copy</strong> that block when it initializes the parameter for that call. The called function or method has the responsibility to copy that block itself if needed.</p> <p>Where ARC does copy blocks automatically is when you are <strong>returning</strong> a block from a function or method. In that case, the compiler knows that it <strong>must</strong> do a copy to the heap for you, and so it does.</p> <p>So your setter should be doing a block copy, even with ARC.</p> <p>I hope that helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POblocks and ARC - copy or crash with release build (caused by optimization level)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USFiroze Lafeer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POblocks and ARC - copy or crash with release build (caused by optimization level)
      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. COWhat I don't understand is why his `callbackBlock = block;` line doesn't implicitly behave like `callbackBlock = [block retain];` in ARC? (provided his `callbackBlock` declaration isn't `__weak`)
      singulars
      1. PO
      1. USMechEthan
    2. COIt probably is retaining the block, but it isn't copying it. That's the problem, because the stack based block is gone before it is used later. The block here needs to be copied, not retained.
      singulars
      1. PO
      1. USFiroze Lafeer
    3. COAhhh, I'd read everything and come to mostly the same conclusions as you, but that one bit was still confusing me. Thank you!
      singulars
      1. PO
      1. USMechEthan
 

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