Initial import.

* Initial import.

svn path=/trunk/; revision=2

AUTHORS

+Jürg Billeter <j@bitron.ch>

INSTALL

+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006 Free Software Foundation, Inc.
+
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+Some systems require unusual options for compilation or linking that the
+`configure' script does not know about.  Run `./configure --help' for
+details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you can use GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+Installation Names
+==================
+
+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+There may be some features `configure' cannot figure out automatically,
+but needs to determine by the type of machine the package will run on.
+Usually, assuming the package is built to be run on the _same_
+architectures, `configure' can figure that out, but if it prints a
+message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+If you want to set default values for `configure' scripts to share, you
+can create a site shell script called `config.site' that gives default
+values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug.  Until the bug is fixed you can use this workaround:
+
+     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+     Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

MAINTAINERS

+Jürg Billeter
+E-mail: j@bitron.ch
+Userid: juergbi
+

Makefile.am

+NULL =
+
+SUBDIRS = \
+	gee \
+	$(NULL)
+
+pkgconfigdir = $(libdir)/pkgconfig
+pkgconfig_DATA = gee-1.0.pc
+
+EXTRA_DIST = \
+	MAINTAINERS \
+	gee-1.0.pc.in \
+	$(NULL)
+

README

+libgee is a collection library providing GObject-based interfaces and
+classes for commonly used data structures.
+
+libgee provides the following interfaces:
+
+	* Iterable
+	  * Collection
+	    * List
+	    * Set
+	* Iterator
+	* Map
+
+The ArrayList, HashSet, and HashMap classes provide a reasonable sample
+implementation of the List, Set, and Map interfaces. ReadOnlyCollection,
+ReadOnlyList, ReadOnlySet, and ReadOnlyMap are read-only wrapper classes
+that prevent modification of the underlying collection.
+
+libgee is written in Vala and can be used like any GObject-based C library.
+It's planned to provide bindings for further languages.
+

autogen.sh

+#!/bin/sh
+
+srcdir=`dirname $0`
+test -z "$srcdir" && srcdir=.
+
+ORIGDIR=`pwd`
+cd $srcdir
+
+autoreconf -v --install || exit 1
+cd $ORIGDIR || exit $?
+
+$srcdir/configure "$@"

configure.ac

+AC_INIT([vala], [0.1.0], [j@bitron.ch], [libgee])
+AC_CONFIG_SRCDIR([Makefile.am])
+AC_CONFIG_HEADERS(config.h)
+AM_INIT_AUTOMAKE([dist-bzip2])
+
+# Checks for programs.
+AC_PROG_CC
+AM_PROG_CC_C_O
+AC_DISABLE_STATIC
+AC_PROG_LIBTOOL
+
+AC_PATH_PROG(VALAC, valac, valac)
+AC_SUBST(VALAC)
+
+AC_SUBST(CFLAGS)
+AC_SUBST(CPPFLAGS)
+AC_SUBST(LDFLAGS)
+
+GLIB_REQUIRED=2.10.0
+
+PKG_CHECK_MODULES(GLIB, glib-2.0 >= $GLIB_REQUIRED gobject-2.0 >= $GLIB_REQUIRED)
+AC_SUBST(GLIB_CFLAGS)
+AC_SUBST(GLIB_LIBS)
+
+AC_CONFIG_FILES([Makefile
+           gee-1.0.pc
+           gee/Makefile])
+
+AC_OUTPUT

gee-1.0.pc.in

+prefix=@prefix@
+exec_prefix=@exec_prefix@
+libdir=@libdir@
+includedir=@includedir@
+datarootdir=@datarootdir@
+datadir=@datadir@
+
+Name: libgee
+Description: The GObject collection library
+Version: @VERSION@
+Requires: glib-2.0 gobject-2.0
+Libs: -L${libdir} -lgee
+Cflags: -I${includedir}/gee-1.0

gee/Makefile.am

+NULL =
+
+INCLUDES = \
+	$(GLIB_CFLAGS) \
+	$(NULL)
+
+BUILT_SOURCES = gee.vala.stamp
+
+lib_LTLIBRARIES = \
+	libgee.la
+	$(NULL)
+
+libgee_la_SOURCES = \
+	gee.vala.stamp \
+	arraylist.c \
+	arraylist.h \
+	arraylist.vala \
+	collection.c \
+	collection.h \
+	collection.vala \
+	hashmap.c \
+	hashmap.h \
+	hashmap.vala \
+	hashset.c \
+	hashset.h \
+	hashset.vala \
+	iterable.c \
+	iterable.h \
+	iterable.vala \
+	iterator.c \
+	iterator.h \
+	iterator.vala \
+	list.c \
+	list.h \
+	list.vala \
+	map.c \
+	map.h \
+	map.vala \
+	readonlycollection.c \
+	readonlycollection.h \
+	readonlycollection.vala \
+	readonlylist.c \
+	readonlylist.h \
+	readonlylist.vala \
+	readonlymap.c \
+	readonlymap.h \
+	readonlymap.vala \
+	readonlyset.c \
+	readonlyset.h \
+	readonlyset.vala \
+	set.c \
+	set.h \
+	set.vala \
+	$(NULL)
+
+geeincludedir = $(includedir)/gee-1.0/gee
+
+geeinclude_HEADERS = \
+	arraylist.h \
+	collection.h \
+	gee.h \
+	hashmap.h \
+	hashset.h \
+	iterable.h \
+	iterator.h \
+	list.h \
+	map.h \
+	readonlycollection.h \
+	readonlylist.h \
+	readonlymap.h \
+	readonlyset.h \
+	set.h \
+	$(NULL)
+
+gee.vala gee.vala.stamp: $(filter %.vala,$(libgee_la_SOURCES))
+	$(VALAC) --library gee $^
+	touch $@
+
+libgee_la_LIBADD = \
+	$(GLIB_LIBS) \
+	$(NULL)
+
+vapidir = $(datadir)/vala/vapi
+
+gee-1.0.vala: gee.vala
+	cp $^ $@
+
+dist_vapi_DATA = \
+	gee-1.0.vala \
+	$(NULL)
+
+EXTRA_DIST = gee.vala.stamp

gee/arraylist.vala

+/* arraylist.vala
+ *
+ * Copyright (C) 2004-2005  Novell, Inc
+ * Copyright (C) 2005  David Waite
+ * Copyright (C) 2007  Jürg Billeter
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * Lesser General Public License for more details.
+
+ * You should have received a copy of the GNU Lesser General Public
+ * License along with this library; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301  USA
+ *
+ * Author:
+ * 	Jürg Billeter <j@bitron.ch>
+ */
+
+using GLib;
+
+/**
+ * Arrays of arbitrary elements which grow automatically as elements are added.
+ */
+public class Gee.ArrayList<G> : Iterable<G>, Collection<G>, List<G> {
+	public int size {
+		get { return _size; }
+	}
+
+	public EqualFunc equal_func {
+		set { _equal_func = value; }
+	}
+
+	private G[] _items = new G[4];
+	private int _size;
+	private EqualFunc _equal_func;
+
+	// concurrent modification protection
+	private int _stamp = 0;
+
+	public ArrayList (construct EqualFunc equal_func = GLib.direct_equal) {
+	}
+
+	public Gee.Iterator<G> iterator () {
+		return new Iterator<G> (this);
+	}
+
+	public bool contains (G item) {
+		return (index_of (item) != -1);
+	}
+
+	public int index_of (G item) {
+		for (int index = 0; index < _size; index++) {
+			if (_equal_func (_items[index], item)) {
+				return index;
+			}
+		}
+		return -1;
+	}
+
+	public G get (int index) {
+		assert (index >= 0 && index < _size);
+
+		return _items[index];
+	}
+
+	public void set (int index, G item) {
+		assert (index >= 0 && index < _size);
+
+		_items[index] = item;
+	}
+
+	public bool add (G item) {
+		if (_size == _items.length) {
+			grow_if_needed (1);
+		}
+		_items[_size++] = item;
+		_stamp++;
+		return true;
+	}
+
+	public void insert (int index, G item) {
+		assert (index >= 0 && index <= _size);
+
+		if (_size == _items.length) {
+			grow_if_needed (1);
+		}
+		shift (index, 1);
+		_items[index] = item;
+		_stamp++;
+	}
+
+	public bool remove (G item) {
+		for (int index = 0; index < _size; index++) {
+			if (_equal_func (_items[index], item)) {
+				remove_at (index);
+				return true;
+			}
+		}
+		return false;
+	}
+
+	public void remove_at (int index) {
+		assert (index >= 0 && index < _size);
+
+		_items[index] = null;
+
+		shift (index + 1, -1);
+
+		_stamp++;
+	}
+
+	public void clear () {
+		for (int index = 0; index < _size; index++) {
+			_items[index] = null;
+		}
+		_size = 0;
+		_stamp++;
+	}
+
+	private void shift (int start, int delta) {
+		assert (start >= 0 && start <= _size && start >= -delta);
+
+		_items.move (start, start + delta, _size - start);
+
+		_size += delta;
+	}
+
+	private void grow_if_needed (int new_count) {
+		assert (new_count >= 0);
+
+		int minimum_size = _size + new_count;
+		if (minimum_size > _items.length) {
+			// double the capacity unless we add even more items at this time
+			set_capacity (new_count > _items.length ? minimum_size : 2 * _items.length);
+		}
+	}
+
+	private void set_capacity (int value) {
+		assert (value >= _size);
+
+		_items.resize (value);
+	}
+
+	private class Iterator<G> : Gee.Iterator<G> {
+		public ArrayList<G> list {
+			set {
+				_list = value;
+				_stamp = _list._stamp;
+			}
+		}
+
+		private ArrayList<G> _list;
+		private int _index = -1;
+
+		// concurrent modification protection
+		public int _stamp = 0;
+
+		public Iterator (construct ArrayList! list) {
+		}
+
+		public bool next () {
+			assert (_stamp == _list._stamp);
+			if (_index < _list._size) {
+				_index++;
+			}
+			return (_index < _list._size);
+		}
+
+		public G get () {
+			assert (_stamp == _list._stamp);
+
+			if (_index < 0 || _index >= _list._size) {
+				return null;
+			}
+
+			return _list.get (_index);
+		}
+	}
+}
+

gee/collection.vala

+/* collection.vala
+ *
+ * Copyright (C) 2007  Jürg Billeter
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of