Good things come to those who vote! Login and vote now.
By bloid
via stainlesscode.com
Submitted: Apr 08 2008 / 15:03
Don’t get me wrong: I’m a huge fan of Apple, Mac computers and OS X. With few exceptions Macs are some of the finest computers around: elegant in design, well engineered, easy to use and friendly to advanced users.
-
Errors That Can Jeopardize the Success of Your Website
-
Simple Tabs w/ CSS & jQuery
-
Using ADF Faces 11g Skinning for setting the styles of specific component instances or groups of instances
-
For Web Apps, Performance Remains an Uphill Battle
-
EveryBlock source code released!
-
W3C dumps XHTML 2 in favor of HTML 5
Comments
bscarr replied ago:
Has this post been taken down? All I can see is a message that says "No blogs posted yet" :-(
ararog replied ago:
+1 :(
donarb replied ago:
If you google for the title, you'll find the cached article. Basically, he's complaining that ObjC does not prevent illegal array accesses (like Java does!) and he spent 6 hours debugging it. He claims there was no indication of a problem, but that's just plain wrong. During debugging, the program will spit out a message to the console every time you get an illegal array access.
Maybe that's why he pulled it.
Dan Stieglitz replied ago:
Hi, this is the author of the original blog post.
Actually it's true that there was no error message... I was using C-style arrays, not NSArray or any subclasses of NSArray. Being new to Objective-C I was unclear as to what method was best to use. Someone had posted a comment indicating that when you use regular C-arrays, array boundaries are not checked. To get errors when using arrays you need to use NSArray or a subclass.
bloid replied ago:
Yeah... looks like article has been pulled... I'll remove this link as well
Voters For This Link (6)
Voters Against This Link (4)