PDR: Objective C Tutorial

Go up to the Tutorials table of contents page

Throughout this semester, we have studied C++, which was one way to add object oriented programming capability to the C programming language. There are other languages that also do that: the one that we will study in this pre-lab is Objective C. The others are described here. Objective C had mostly died out as a language that was widely used until Apple decided to use it for their iPhone (and now iPad) application development. We want you to be familiar with it, so that you can see a different way to allow for object oriented programming using a C-like language.

But, why?

Wait a minute – isn’t Objective C a dying programming language?

Well, yes and no. Objective C was exclusively used to implement iOS apps (i.e., iPad, iPhone, and iPod) . But with the recent advent of Swift, more people are moving toward that and away from Objective C. So while Objective C is seeing a decline in how much it is used, it is not going anywhere anytime soon.

However, the point of having this tutorial is not about being an iOS developer – instead, it’s to show you that there is another way to add objects to C other than C++.

Objective C Installation

The first part of the pre-lab is to make sure you have access to a compilation environment for Objective C.

The course VirtualBox image has Objective C properly installed. The lab machines in 001 have Objective C installed. If you are familiar with ssh (or SecureCRT), you can remotely log in to labunix01.cs.virginia.edu, and write your program there (the login is the same as your 001 Linux login).

First, we need to see if we can compile a helloworld.m (src) program. The compilation line is clang helloworld.m -lobjc (that command will change later on, but for now it’s fine).

Linux: Install the gobjc package (and any dependencies), which should allow Objective C compilation.

Mac OS X: Try it out from the command line, as it may just work. If it doesn’t work, then you may have to install a bunch of developer packages. It would likely be far easier to boot up the VirtualBox image for this one tutorial. Note that some students reported that they needed to include the -arch i386 flag to the compiler, but we did not need it on our Mac OS X test systems.

If you are having problems getting the compilation to work for you, come speak to us! Don’t spend hours and hours banging your head against the wall. And you probably shouldn’t wait until the last minute to try out the compilation commands…

Compiling an Objective C program

To compile your code on either Mac OS X or Linux, enter clang *.m -lobjc. With C++, you would compile all of your .cpp files (*.cpp); with Objective C, you compile all of your .m files (hence, *.m). Note that you will use a longer compilation command later, which is described below. Since this is not Objective C++ (which does exist), we are using clang instead of clang++. You should put the -lobjc part in there – that tells clang to link your code to the Objective C library to allow your program to run. Note that some platforms will not need the -lobjc line, but others will, and it doesn’t hurt to put it in anyway.

Enter the following hello world program into a helloworld.m (src) file – Objective C uses .h files for the interfaces (i.e., header files), just like C++ does. For the implementation files, however, Objective C uses a .m extension instead of the .cpp extension that C++ uses.

#import <stdio.h>
int main (void) {
    printf ("Hello world!\n");
}

The only difference between that program and a normal C program is the use of #import instead of #include. The compilation command is clang helloworld.m -lobjc.

Learn Objective C

READ THROUGH THE NEXT SECTION BEFORE YOU START READING THESE TUTORIAL LINKS!

The tutorials that we will be using come from Wikibooks, and can be found here. The first section (“Objective-C concepts”) discusses such things as what is OOP, and what is an object. You can probably skip that part. The second section (“Getting Started”) talks about how to compile a hello world program, which we have done above, so you can skip that part as well.

The tutorial for this week is the following two sections: Objective C Syntax and Objective C: In Depth. While we won’t expect you to be experts on Objective C after this lab, we will expect you to be familiar with the material at those two URLs. The first one is what is necessary to write the program for this tutorial; the second is good information to know (i.e. makes a great final exam question), but probably not necessary for the pre-lab program. Our solution code for this pre-lab did not use any of the material from the in-depth tutorial.

If you are interested in the history of Objective C, and why it’s used on the Apple platforms (including the iPhone and iPad), see the History section of the Wikipedia article on Objective C (this is not required reading).

Differences with the Wikibooks Tutorials

The tutorials on Wikibooks are sufficient for this tutorial. However, there are a few changes that MUST be made for your program to compile and run properly! There are five differences to keep in mind. The rest of the tutorials are valid, but the changes mentioned here will need to always differ from what the tutorial states.

Difference 1: the #import line

The Objective C Syntax tutorial on Wikibooks has the following #import line (this is the first line of the Point.h file):

#import <objc/Object.h>

In our installations, both on the Linux VirtualBox image and on Mac OS X, we will replace that with the following:

#import <Foundation/NSObject.h>

Difference 2: the super-class

We have included (well, imported) a different file, and thus can no longer subclass from Object. Thus, we must change the super class name from Object to NSObject. This is line 3 of the Point.h class in the Objective C Syntax tutorial on Wikibooks.

Difference 3: compilation command

As our programs are now more complicated than just a “hello world”, the compilation line is longer as well. The compilation command for Linux machines (such as VirtualBox image) is:

clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/7/include/ *.m -lobjc -lgnustep-base

The command above was tested on the provided Virtual Box image and works. If you are on another Linux system, you can try one of the following similar commands to see if they work:

clang -I /usr/include/GNUstep/ *.m -lobjc -lgnustep-base
clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/5/include/ *.m -lobjc -lgnustep-base

For other Linux distributions you may need to install one or more of the follow packages: gnustep, gnustep-make, gnustep-devel. To install with apt run

sudo apt install <PACKAGE_NAME>

Where <PACKAGE_NAME> is one or more of the packages listed above.

On Mac OS X, the compilation command is much simpler, and is what was previously shown. Here it is again for your convenience:

clang *.m -lobjc

Difference 4: other libraries to use

If you are compiling the Point class, described in the Objective C Syntax tutorial on Wikibooks, the compiler will need to know what the sqrt() function is. Thus, you will have to link it to the math library: put -lm at the end of the compilation command, otherwise it will tell you that it cannot find the sqrt() implementation. This likely won’t be necessary for the program you have to do below, but it will be necessary for the Point class program.

Difference 5: use release instead of free

To deallocate an object, use release instead of free. In other words, [temp free]; will not work (which is what the tutorial states), but [temp release]; will work properly.

Hack some Objective C code

What tutorial would be complete without a data structure to implement?

Your task is to implement a data structure in Objective C – a very simple singly linked list for integers. The program is basically the same as that which was required in the C tutorial. The requirements for the program are:

Read in an integer, which we’ll call n
Read in n more ints, and put those into a linked list
- The linked list must be dynamically allocated
Print out that linked list (we don’t care the order)
Properly deallocate the linked list

The program should be in a file called linkedlist.m (although see the note about the filenames, below). A sample execution run might look like the following:

Enter how many values to input: 4
Enter value 1: 2
Enter value 2: 4
Enter value 3: 6
Enter value 4: 8
8
6
4
2

You will need to implement ONE class, ListNode (or whatever you would like to call it). And a main() method, of course. You can put all of your code in one file (put the interface first, then the implementation, then the main()), or you can separate it out into separate files (such as listnode.m, listnode.h, and main.m).

The linked list program will need to be submitted as part of the lab; no Makefile is being submitted. As long as it compiles with the following compilation command, we really don’t care what the files are named (within reason). The compile command that we will use to compile your code on Linux is clang -I /usr/include/GNUstep/ *.m -lobjc -lgnustep-base; this is equivalent to clang *.m -lobjc on Mac OS X.

This is not meant to be a complicated program! We don’t care about the order that the list is printed (forward or reverse is fine); you don’t need to implement iterators, or anything too complicated. Our code had just main() method, and a ListNode class with a handful of methods. Your insert() code should be in main(), not in your class. Likewise your code to remove the elements, and to print the list should be in main().

A few requirements for the program:

It must have a ListNode (or whatever you want to call it) class, which must have some basic methods: getters, setters, that sort of thing.
You do not need to implement a List class; you can directly create (and destroy) ListNode objects right from your main() function.
Since this is not Objective C++, it will need to use C input and output, so printf() and scanf() are your friends
You are welcome to have a default constructor, and call two separate setter method (to set, presumably, the value and the next fields of the ListNode). Or you can call a constructor with two parameters; it’s your choice (the former is a bit easier). The Point class in the Wikibooks tutorial does the former.
It must print out what it is doing, and show the resulting list (or return value), so that we can follow what is going on. See the sample output, above, for an example. Your output need not match ours, but we must be able to tell what is going on from the output.
The point of this pre-lab is to work with calling various methods in Objective C (getters, setters, etc.). Directly accessing the fields is not what we are looking for.

A few notes while working on the program:

Pointers can point to Objective C types (objects, structs, etc.) just like in C and C++
See the Point class, in the Wikibooks syntax tutorial, for a code class example.
The this pointer in Objective C is called self
The NULL pointer in C++ is called nil in Objective C
Be careful about naming your list class “List” if you are using Mac OS X, as it will conflict with the List class already declared in an existing library. Name it something else.
An object is deleted by calling the dealloc method, which is automatically inherited by all classes. You should NOT call dealloc anywhere in your code – dealloc is called by the Objective C runtime (in a similar way the destructor is called when an object goes out of scope in C++). To create a custom destructor, override the dealloc method, and just call super dealloc as the last command of that destructor. But you probably don’t need a custom constructor for this program. To indicate to the runtime that you are no longer using the object, call release on that object (e.g., [myObj release]).

Constructors

Constructors are not explained very well in the tutorial, so we describe them a bit here.

For complicated classes, you definitely are going to want a constructor. But for a simple class – and your ListNode class is certainly simple – you can just use the default constructor. It doesn’t set the fields, but you can promptly set them once the object has been created. Like C++, if you don’t declare any constructors, then the default one is automatically included.

In Objective C, constructors are just functions that start with “init” (for convenience sake), and return a pointer to the type we are constructing. Typically, the first line in constructor is [super init];, which will call the parent’s constructor. The last line is typically return self;. There is no special handling for constructors as there is in Java or C++.

You call the default constructor (init()) by the syntax:

ListNode *node = [[ListNode alloc] init];

Note that this can be shortened to:

ListNode *node = [ListNode new];

This is how it is declared in the tutorials on Wikibooks, but this is just a shorthand for the alloc/init version shown first. Note that you do not need to declare a default constructor - one is provided for you automatically, just like C++.

To create a specific constructor, you create it as you would any other method with parameters, and it is typically named starting with “init”. It is called similar to the alloc/init format described above:

ListNode *node = [[ListNode alloc] initWithValue: v];

The WithValue: v is the new part in the calling of the specific constructor.