Objective-C Sandbox - Revision history

WikiSysop at 02:37, 12 July 2013

2013-07-12T02:37:19Z

WikiSysop at 04:33, 3 April 2013

2013-04-03T04:33:07Z

WikiSysop: /* iOS: A self directed course of study */

2013-03-02T07:12:57Z

‎iOS: A self directed course of study

WikiSysop at 06:09, 2 March 2013

2013-03-02T06:09:23Z

WikiSysop: /* ARC */

2013-03-02T05:27:59Z

‎ARC

WikiSysop at 05:27, 2 March 2013

2013-03-02T05:27:11Z

WikiSysop: /* Property */

2013-03-02T05:07:44Z

‎Property

WikiSysop: /* I've given up on trying to follow properly so i'm just googling hints now */

2013-03-02T05:06:38Z

‎I've given up on trying to follow properly so i'm just googling hints now

WikiSysop: /* The C Comparisions are lost upon me but maybe at a later date this will make more sense */

2013-03-02T05:05:44Z

‎The C Comparisions are lost upon me but maybe at a later date this will make more sense

WikiSysop: /* The C Comparisions are lost upon me but maybe at a later date this will make more sense */

2013-03-02T05:05:02Z

‎The C Comparisions are lost upon me but maybe at a later date this will make more sense

← Older revision		Revision as of 02:37, 12 July 2013
Line 89:		Line 89:

	* http://iosdevscout.com/		* http://iosdevscout.com/
		+
		+	== See Also ==
		+
		+	[[Category:Programming]]

@@ Line 1: / Line 1: @@
 == A haphazardly conducted class ==
 === Hello World ===
 * Open Xcode
@@ Line 16: / Line 19: @@
 * Published a hello world screen in the simulator
 [[Image:iosoptions4.png]]
 === Traces ===

@@ Line 82: / Line 82: @@
 * [http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphone101/Articles/00_Introduction.html Your 1st iOS app - A Guide!]
 The @autoreleasepool statement supports the Automatic Reference Counting (ARC) system. ARC provides automatic object-lifetime management for your app, ensuring that objects remain in existence for as long as they're needed and no longer.
 * http://iosdevscout.com/

← Older revision		Revision as of 06:09, 2 March 2013
Line 84:		Line 84:

	The @autoreleasepool statement supports the Automatic Reference Counting (ARC) system. ARC provides automatic object-lifetime management for your app, ensuring that objects remain in existence for as long as they're needed and no longer.		The @autoreleasepool statement supports the Automatic Reference Counting (ARC) system. ARC provides automatic object-lifetime management for your app, ensuring that objects remain in existence for as long as they're needed and no longer.
		+
		+	* http://iosdevscout.com/

@@ Line 79: / Line 79: @@
 I've stopped following the class due to general confusion and inability to understand the accent.
-* http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphone101/Articles/00_Introduction.html
+== iOS: A self directed course of study ==
 The @autoreleasepool statement supports the Automatic Reference Counting (ARC) system. ARC provides automatic object-lifetime management for your app, ensuring that objects remain in existence for as long as they're needed and no longer.

← Older revision		Revision as of 05:27, 2 March 2013
Line 74:		Line 74:

	"By default, property accessors are atomic."		"By default, property accessors are atomic."
		+
		+	=== ARC ===
		+
		+	I've stopped following the class due to general confusion and inability to understand the accent.
		+
		+	* http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphone101/Articles/00_Introduction.html
		+
		+	The @autoreleasepool statement supports the Automatic Reference Counting (ARC) system. ARC provides automatic object-lifetime management for your app, ensuring that objects remain in existence for as long as they're needed and no longer.

← Older revision		Revision as of 05:07, 2 March 2013
Line 72:		Line 72:

	What "atomic" does not do is make any guarantees about thread safety. If thread A is calling the getter simultaneously with thread B and C calling the setter with different values, thread A may get any one of the three values returned -- the one prior to any setters being called or either of the values passed into the setters in B and C. Likewise, the object may end up with the value from B or C, no way to tell."</i>		What "atomic" does not do is make any guarantees about thread safety. If thread A is calling the getter simultaneously with thread B and C calling the setter with different values, thread A may get any one of the three values returned -- the one prior to any setters being called or either of the values passed into the setters in B and C. Likewise, the object may end up with the value from B or C, no way to tell."</i>
		+
		+	"By default, property accessors are atomic."

@@ Line 55: / Line 55: @@
 The hungry developers in the room are hungry and confused.
-=== I've given up on trying to follow properly so i'm just googling hints now ===
+=== Property ===
 <pre>@property (nonatomic, strong) NSString *noteTitle;
@@ Line 61: / Line 63: @@
 @property (nonatomic, weak) UILabel *noteLabel;</pre>
-<b> From internet - the difference between atomic and nonatomic</b>
+<b>What is difference between atomic and nonatomic</b>
 "Assuming that you are @synthesizing the method implementations, atomic vs. non-atomic changes the generated code. If you are writing your own setter/getters, atomic/nonatomic/retain/assign/copy are merely advisory. (Note: @synthesize is now the default behavior in recent versions of LLVM. There is also no need to declare instance variables; they will be synthesized automatically, too, and will have an _ prepended to their name to prevent accidental direct access).
 With "atomic", the synthesized setter/getter will ensure that a whole value is always returned from the getter or set by the setter, regardless of setter activity on any other thread. That is, if thread A is in the middle of the getter while thread B calls the setter, an actual viable value -- an autoreleased object, most likely -- will be returned to the caller in A.
@@ Line 68: / Line 71: @@
 In nonatomic, no such guarantees are made. Thus, nonatomic is considerably faster than "atomic".
-What "atomic" does not do is make any guarantees about thread safety. If thread A is calling the getter simultaneously with thread B and C calling the setter with different values, thread A may get any one of the three values returned -- the one prior to any setters being called or either of the values passed into the setters in B and C. Likewise, the object may end up with the value from B or C, no way to tell."
+What "atomic" does not do is make any guarantees about thread safety. If thread A is calling the getter simultaneously with thread B and C calling the setter with different values, thread A may get any one of the three values returned -- the one prior to any setters being called or either of the values passed into the setters in B and C. Likewise, the object may end up with the value from B or C, no way to tell."</i>

← Older revision		Revision as of 05:05, 2 March 2013
Line 52:		Line 52:

	movieName(char * movieName, char * actorName);</pre>		movieName(char * movieName, char * actorName);</pre>
		+
		+	The hungry developers in the room are hungry and confused.

	=== I've given up on trying to follow properly so i'm just googling hints now ===		=== I've given up on trying to follow properly so i'm just googling hints now ===