Skip to main content

Our first list.

For our list of primes we need a list (naturally).  The best way to understand data structures is to implement them in a low level language.  Since I don't feel like inflicting ASM on everyone (although I do like assembler) we will use the next best thing.  C

Out list needs a data element (the found prime) and a pointer to the next element.
In C that looks like this.

struct prime_elem_s {
  uint64_t prime;
  struct prime_elem_s *next;
};
typedef struct prime_elem_s prime_elem_t;

We define a structure containing the current prime and a pointer to the next element.  Then we define a type prime_elem_t to refer to that structure.

In this case we want to add elements to the end of the list so we will also need a tail pointer.  We will create a list header which will keep a head and tail pointer as well as the number of elements in the list.

typedef struct {
  uint64_t length;
  prime_elem_t *head;
  prime_elem_t *tail;
} prime_list_t;

Now we can write a function which appends a new prime to the list.

void push_prime(prime_list_t *prime_list, uint64_t prime)
{
  prime_elem_t *elem = malloc(sizeof(prime_elem_t));

  elem->prime = prime;
  elem->next = NULL;

  if( prime_list->tail )
    {
      prime_list->tail->next = elem;
      prime_list->tail = elem;
    }
  else
    {
      prime_list->head = prime_list->tail = elem;
    }
  prime_list->length++;
}

Here we:
  1. allocate a new element
  2. initialize its fields
  3. if this isn't the first element then append it to the list's tail then update the tail pointrewolf
  4. otherwise set both the head and tail to the new element
  5. increment the list's length

Comments

Popular posts from this blog

Duck typing considered harmful.

I've had a chance to work on a fairly large chunk of Python at this point and have decided that Python (like Perl) is completely untenable at scale.  <rant><rave><drool>  but wait!  I have reasons! Programmers spend most of their time reading code.  We read massive amounts of code.  After we read massive amounts of code we write one... or change one... To make a change to a piece of code you first have to understand what it does and how it interacts with the system around it.  Then we start reading massive amounts of code again.  Anything you can do to minimize the amount of code a programmer has to understand to make a change becomes a huge gain in productivity. Duck typing causes the amount of code you need to read to make a change to grow very large. For example lets look at two functions, one in C++ and one in Python. First in C++ int function(type1 arg1, type2 arg2) {   return arg1->method(arg2); } In this fun...

Publications by Jeff Vitter

Jeff Vitter is the provost and executive vice chancellor and the Roy A. Roberts Distinguished Professor at the University of Kansas. I just stumbled across his page and found a great book on external memory algorithms and data structures external memory algorithms and data structures. IE: algorithms and data structures to use when your dataset is too large to fit in main memory. He has many other papers on his site including several on external memory graph algorithms. Here's the link... http://www.ittc.ku.edu/~jsv/Papers/catalog/

Types of arrays

Arrays are one of the earliest data structures.  They are essentially just a block of memory which is accessed by offset.  Despite their simplicity there are still several broad categories each with their own sets of algorithms. Is the array a fixed size or can it grow as you add elements to it? A fixed size array is called a static array and one that can grow is called a dynamic array. Are the element all of the same type or can they be different? If they must all be the same type then the array are called homogeneous.  Otherwise it is a heterogeneous array. Finally, how many dimensions (subscripts) does the array have? For example, a 2 dimensioned array is a matrix. The number of dimensions doesn't change the structure of the array but changes the way elements are accessed.