Chuck Norris on Java Programming

This has got to be one of the funniest things I have ever heard:

(pasted from) http://www.ovisual.com/4/

• Chuck Norris can make a class that is both abstract and final.
• Chuck Norris serializes objects straight into human skulls.
• Chuck Norris doesn’t deploy web applications, he roundhouse kicks them into the server.
• Chuck Norris always uses his own design patterns, and his favorite is the Roundhouse Kick.
• Chuck Norris could use anything in java.util.* to kill you, including the javadocs.
• Chuck Norris can hit you so hard your web app will turn into a swing application, and a very bad swing application containing lots of icons of human skulls.
• Chuck Norris demonstrated the meaning of Float.POSITIVE_INFINITY by counting to it, twice.
• A synchronize doesn’t protect against Chuck Norris, if he wants the object, he takes it.
• Chuck Norris doesn’t use javac, he codes java by using a binary editor on the class files.
• Chuck Norris’ java code never needs to be optimized. His code is so fast that it broke the speed of light during a test run in Sun’s labs killing 37 people.
• When someone attempts to use one of Chuck Norris’ deprecated methods, they automatically get a roundhouse kick to the face at compile time.
• The java.lang package originally contained a ChuckNorris class, but it punched its way out the package during a design review and roundhouse kicked Bill Joy in the face.
• Chuck Norris never has a bug in his code, EVER!
• Chuck Norris doesn’t write code. He stares at a computer screen until he gets the progam he wants.
• Code runs faster when Chuck Norris watches it.
• Chuck Norris’ binary edited classes ignore Java bytecode verifier.
• Chuck Norris methods doesn’t catch exceptions becuase no one has the guts to throw any at them.
• Chuck Norris will cast a value to any type just by staring at it.
• If you get a ChuckNorrisException you’ll probably die.
• Chuck Norris is the only one who can use goto and const in Java.
• Chuck Norris can compile Java code in .NET Framework, obviously just by staring at it.
• Chuck dont need to catch an Exception because Java is afraid of the “flying tornado kick” at the moment it throws
• Chuck Norris’s code can roundhouse kick all other Java Objects’ privates
• Java visibility levels are public, default, protected, private and “protected by Chuck Norris”, don’t try to access a field with this last modifier!!
• Chuck Norris eats JavaBeans and Roundhouse Kicks JavaServer Faces!
• Chuck Norris can divide by 0!
• Garbage collector only runs on Chuck Norris code to collect the bodies.
• Chuck Norris code uses agressive heap natively
• Every single line code of Chuck Norris runs in real time. Even in a multi threading application.
• When a CPU load a Chuck Norris class file, it doubles the speed.
• Chuck Norris can execute 64bit lenght instructions in a 32bit CPU.
• Chuck Norris implements “Indestructible”. All the other creatures implements “Killable”.
• Chuck Norris only program Java web applications to get a .WAR in the end.
• Chuck Norris once roundhouse kicked a Java class very hard. The result is known as a inner class.
• Chuck Norris can do multiple inheritance in Java.
• JVM never throws exceptions to Chuck Norris, not anymore. 753 killed Sun engineers is enough.
• Chuck Norris doesn’t need unit tests because his code always work. ALWAYS.
• Chuck Norris extends God.
• Chuck Norris workstation has so memory and it’s so powerful that he could run all java applications in the world and get 2% of resources usage.
• Chuck Norris codes generics since 1.3.
• Chuck Norris’ classes can’t be decompiled… don’t bother trying.

iPhone Application Development: Memory Management - Part 2

Re read the earlier post about Memory Management. Lots of new stuff and new understanding has been added to the earlier post. It should really be an article in itself.

iPhone Application Development: Collections

Apple provides three basic collection classes: NSArray, NSSet, and NSDictionary. All three of these classes are non-mutable. i.e. once created, they cannot be changed. Their mutable equivalents are NSMutableArray, NSMutableSet, and NSMutableDictionary. All collections store objects only - primitive types can be wrapped in NSNumber and stored in collections.

NSArray is used to store lists of objects. An Ordered Collection. Primitive types can be wrapped in NSNumber. Common operations are supported: count, objectAtIndex, containsObject, etc. NSMutableArray contains additional operations: addObject, insertObject... atIndex, removeObject, removeObjectAtIndex, etc.

NSSet is a set of Objects. An Unordered Collection. An object might appear a maximum of one time. Operations supported are similar to NSArray.

NSDictionary: are equivalent to Map in Java. They store key, value pairs. Both keys and values are objects. Common supported operations: count, objectForKey, allKeys. NSMutableDictionary also supports editing operations such as setObject... forKey, removeObjectForKey.

NSDictionary supports saving to (writeToFile) and loading from (initWithContentsOfFile) files. These are usually called property lists or plists. The file created would be an XML file. Similarly, initWithContentsOfURL, writeToUrl are supported for URL operations.

Memory Management Reminder: Every collection retains an object when its added, and releases it when it is removed. Releasing a collection object releases all the objects stored in it as well.

iPhone Application Development: Using gdb

gdb is a command line debugger. In addition to XCode providing a graphical debugger, Apple includes the gdb debugger with XCode. Setting a breakpoint is as easy as double clicking in the left margin of XCode. This is similar to Eclipse. For those new to gdb, here are a few basic gdb commands to get you started.


print-object anObj
print-object [anObj description]
print-object [nsStr stringByAppendingString:@" yes"]
print (int) [@"John Galt" length]
print (char *) [nsStr UTF8String]

other commands:
call [exp]: Calls the function
set [var] = [exp]
whatis [variable]: print details about variable
help


iPhone Application Development: Objective-C / Cocoa: String Operations

Apple has provided a very nice implementation of the String class. Called NSString. Any string in Objective-C, written as @"Status" is represented in the code as an instance of NSString. Keep in mind that NSString objects are non-mutable. Just like Java String objects.

Go through NSString.h for many many more methods

NSString *nsStr = @"iPhone Development";
int len = [nsStr length]; // Length of a string
NSString *result = [nsStr stringByAppendingString:anotherNsStr]; Combine 2 strings
NSRange range = [nsStr rangeOfString:@"iPhone"]; // range (not a pointer) would contain location and length of found string
NSString *str = [@"iPhone Application Development" substringFromIndex:7]; // -> Application Development
NSString *str = [@"iPhone Application Development" substringToIndex:6]; // -> iPhone
NSString *str = [@"iPhone Application Development" substringWithRange:NSMakeRange(7, 11)]; // -> Application

NSArray *arrayOfStrings = [@"iPhone Application Development" componentsSeparatedByString:@" "]; // split on space

// Converting between C Strings and NSStrings
NSString *nsStr = [[NSString alloc] initWithUTF8String:"iPhone"];
(const char *)cStr = [nsStr UTF8String];


Mutable Strings: If you need to make modifcations to NSString, use NSMutableString. Some of the valid messages to NSMutableString:


[msMuStr appendString:@" needs an iPhone"];
[msMuStr deleteCharactersInRange:NSMakeRange(7, 11)];
[msMuStr insertString:@" is a good application " atIndex:10];
[msMuStr replaceCharactersInRange:NSMakeRange(7, 11) withString:@" is a good application "];


iPhone Application Development: Memory Management with Objective-C / Cocoa

This discussion touches the basics of memory management within Objective-C / Cocoa. Hopefully, you have already ready my post about differences between C++ / Java and Objective-C.

Cocoa library (and thus Cocoa Touch for iPhone Development) defines NSObject, which is at the root of the entire class hierarchy of the Foundation framework. Every other framework, depends on the Foundation Framework. NSObject implements a semi-automated / reference counting version of garbage collection. Memory manager might be a more appropriate name.

Here is some sample code that helps illustrate how to use NSObject's garbage collection mechanism:

#import <Foundation/Foundation.h>

int main(int argc, char *argv[]) {
NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];

NSObject *obj = [[NSObject alloc] init];
NSLog(@"Created object %@", obj);
[obj release];

[pool release];
return 0;
}

NSObject provides the following messages to manage objects via the memory-manager:

• alloc: Create a new object. Allocates physical memory for the object. This message to be passed to the class. Alloc "retains" the object. i.e. Objects created by alloc have a reference count of 1. Be sure to release it when you are done.
• init: initializes the object. It is considered best practice to always init the object by sending it the init message. Typical object creation looks like MyClass *obj = [[MyClass alloc] init]; - calls both alloc and init.
• If you override init, it must always return itself (id). Sample code: if (self = [super init]) { /* my inits */ } return self;
• dealloc: Free the memory obtained by alloc. Avoid calling dealloc. Always call release - let the memory manager perform dealloc, when appropriate.
• retain: Signal to the garbage collector that we are intrested in this object. This increases the reference counter for this object by one.
• release: Signal to the garbage collector that we are no longer interested in this object. This decreases the reference counter by one. When the reference counter reached 0, the object is deallocated. As a general rule, always "release" pointers holding memory. This will let the memory-manager do its job.
  

NOTE: If you do decide to over-ride any of these methods, be sure to call super's corresponding method at the appropriate time.

Creating an NSAutoReleasePool creates and inits the memory-management system. At the end of the program, the release message to the auto-release pool signals that we are no longer interested in it. The system then disposes off the auto-release pool, and sends release message to all the objects it contains. Any object that gets to a reference count of 0, is deallocated.

General Tips / Rules of thumb related to memory management

• Classes should override dealloc, if they want to be notified of when the object is put out of its misery. This is an appropriate place for the object to release any memory that it may have allocated. Be sure to call parent's dealloc when you are done.
• In setters, always retain the new object first, then release the old object. This will take care of cases when the same value is being set over and over again.
• Maintain atleast one Auto release pool per thread
• If you have to create an object and return it from a method. Make sure you pass the autorelease method to it. This will add the object to the autorelease pool.
• This leads to: don't release objects that you receive from other messages. Assume that they have been added to the auto release pool by the creator. release them *only* if you retain them for some reason.
• Write memory balanced code: total count of alloc, copy, mutableCopy should be equal to the total count of release, autorelease
  
• Every collection retains an object when its added, and releases it when it is removed. Releasing a collection object releases all the objects stored in it as well.
• NSString objects created using @"..." should be considered as constants. retain or release messages have no effect on them.
  

Objective-C for C++ / Java developers

Here I document the differences between Objective-C and another object oriented language like C++ / Java. The goal is to get someone, who has a fair grasp of object oriented concepts in either C++ or Java or (preferably) both, started with understanding / writing Objective-C code as soon as possible. The goal being effective iPhone Development. If you are reading this without any background, please read my previous post about objective-c "hello world" program structure, and creating a first basic class in objective-c.

This blog entry is a work in progress. I will keep updating this as I learn more about objective-c.

Differences between Objective C and C++ / Java.

Concept	C++ / Java	Objective-C	Details
File name extension	.h / .c / .cpp / .java	.h / .m	Declarations in .h file. Implementation in .m
Declaring a method / message	int add(int x, int y)	- (int) add:(int)x with:(int)y	types are always enclosed in brackets
Calling the method / sending a message	int result = obj.add(10, 12);	int result = [obj add:10 with:12];	message name and first parameter are same
Nesting method calls	int r = obj.add(obj.getX(), obj.getY);	int r = [obj add:[obj getX] with:[obj getY]];
Formatting	All printf formats (%s, %d etc)	All C formats, and %@	%@ prints and object's "description"
Calling methods in parent class	super.init();	[super init];
Refering to myself / current object	this.add(10, 12);	[self add:12 with:12];

Other things

• Type (id) represents current class. No need to specify name of the class
• NULL: the keyword "nil" represents a null value.
• Message passing is nil safe. nil elements do not core dump / throw a NullPointerException. Data members are auto-initialized to nil
• All method / message binding in Objective-C is dynamic. Classes maintain a list of messages that will be accepted at runtime. All other messages are passed on to parent. This processing happens at run time.
• For Class level messages, replace the "-" with "+" as the first character of the message declaration and implementation