First commit

Creating git repository.

Author: Leonardo Boshell

.gitignore

@@ -0,0 +1,10 @@
+Makefile
+Makefile.in
+aclocal.m4
+autom4te.cache
+config.log
+config.status
+configure
+discheck.out
+install-sh
+missing

AUTHORS

@@ -0,0 +1 @@
+Leonardo Boshell <[email protected]>

COPYING

@@ -0,0 +1,14 @@
+All the source code and related files distributed with this software have
+been dedicated to the public domain by the authors.
+
+Anyone is free to copy, modify, publish, use, compile, sell, or distribute
+the software, either in source code form or as a compiled binary, for any
+purpose, commercial or non-commercial, and by any means.
+
+Thank you for reading this notice. Inspired by the enlightened words used by
+the authors of another software project, a very popular one, also in the
+public domain, here's a blessing:
+
+  May you find forgiveness for yourself and forgive others.
+  May you experience and share the gift of uncoditional love.
+  May you see light, wherever the illusion of darkness appears.

ChangeLog

@@ -0,0 +1,3 @@
+2007-08-09  Leonardo Boshell  <[email protected]>
+
+	=== Release 0.1.0 ===

HACKING

@@ -0,0 +1,39 @@
+HACKING LitJSON
+
+This software is dedicated to the public domain. This means that you may
+use, modify and distribute the code freely without having to ask for
+permissions of any kind and without the need to follow any particular rules
+or conventions.
+
+If, however, you want to contribute your own changes back to the original
+authors to be redistributed along with any future versions, please note that
+the following two requirements do apply:
+
+a) Your source code should be written in the same coding style used in the
+   original files. This means that any code submitted to be included in
+   the project has to follow the conventions already in use regarding
+   indentation, spaces, casing, file headers and so on.
+   
+   When in doubt, you may submit your contributions as close to the style as
+   you can, and they can be edited before inclusion if necessary.
+
+b) In order to keep this software in the public domain, all new contributors
+   are asked to dedicate their contributions to the public domain. If you
+   want to send a patch or enhancement for possible inclusion, please
+   accompany the patch with the following statement:
+
+     The author or authors of this code dedicate any and all copyright
+     interest in this code to the public domain. We make this dedication for
+     the benefit of the public at large and to the detriment of our heirs
+     and successors. We intend this dedication to be an overt act of
+     relinquishment in perpetuity of all present and future rights to this
+     code under copyright law. 
+
+   If you are currently an employee, it is possible that by law your
+   employer automatically receives the copyright to any and all work that
+   you do, including enhancements you might want to submit to this project.
+   In that case, there's some legal work that has to be done to ensure your
+   patches stay in fact in the public domain. We do not have the means nor
+   the will to handle such a process, but we're open to suggestions. Please
+   contact us if this situation applies to you.
+

INSTALL

@@ -0,0 +1,84 @@
+Installation Instructions
+*************************
+
+
+Basic Installation
+==================
+
+Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package.
+
+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.
+
+
+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.
+
+
+`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.
+

Makefile.am

@@ -0,0 +1,24 @@
+AUTOMAKE_OPTIONS = dist-bzip2 dist-zip no-dist-gzip
+
+SUBDIRS = bin src test data doc
+
+dist-hook:
+	mkdir $(distdir)/benchmarks
+	cp -udpR $(srcdir)/benchmarks/* $(distdir)/benchmarks
+	cd $(distdir)/benchmarks && $(MAKE) distclean
+	@if test "x$(DISTBIN)" != "x"; then  \
+		echo "Creating binary release";  \
+		mkdir -p $(distdir)/bin;         \
+		cd $(srcdir) && $(MAKE);         \
+		cp $(srcdir)/bin/LitJson.dll     \
+			$(distdir)/bin;              \
+		echo > $(distdir)/README.new;    \
+		echo "** Note: This is the binary distribution." >> \
+			$(distdir)/README.new; \
+		echo "** A pre-compiled .dll can be found in the 'bin' directory." >> \
+			$(distdir)/README.new; \
+		echo >> $(distdir)/README.new; \
+		echo >> $(distdir)/README.new; \
+		cat $(srcdir)/README >> $(distdir)/README.new; \
+		mv -f $(distdir)/README.new $(distdir)/README; \
+	fi

NEWS

@@ -0,0 +1,5 @@
+=============   ----------
+LitJSON 0.1.0 | 2007-08-09
+=============   ----------
+
+First release.

README

@@ -0,0 +1,68 @@
+LitJSON
+=======
+
+A .Net library to handle conversions from and to JSON (JavaScript Object
+Notation) strings.
+
+Home page: http://litjson.sourceforge.net/
+
+
+Installation
+------------
+
+See the file INSTALL for generic building and installation instructions.
+
+The 'configure' script for this package recognizes the following specific
+flags:
+
+  --disable-debug
+    Disables the creation of debug binaries (e.g. LitJson.dll.mdb). These
+    are enabled by default.
+
+
+Tests
+-----
+
+This library comes with a set of unit tests using the NUnit framework. The
+'configure' script tries to find the necessary information in order to use
+them.
+
+If everything is set up properly, you may run the tests with 'make check'.
+
+
+Using LitJSON from an application
+---------------------------------
+
+Once this library is compiled and optionally installed in the root
+filesystem, .Net developers may use it by simply copying the .dll file into
+their project's directory.
+
+For those developers using standard Unix tools such as pkg-config and make,
+this library comes with a .pc file to help in the process of consuming it.
+
+One way this could work would be adding a rule in the Makefile (normally
+called 'update-libraries') where the necessary .dll's are copied into the
+project's source directory, and a text file is created with the flags that
+are to be passed to the compiler. Then this text file is used in the rules
+used to compile the project. For example:
+
+
+update-libraries:
+	cp `pkg-config --variable=Libraries litjson` .
+	pkg-config --libs litjson > litjson.flags
+
+Demo.exe: Demo.cs litjson.flags
+	mcs -out:$@ Demo.cs `cat litjson.flags`
+
+
+For more information on this process, please see
+<http://www.mono-project.com/Guidelines:Application_Deployment>, section 2.
+Libraries with Unstable APIs.
+
+
+Bug Reports
+-----------
+
+Please submit all bug reports, feature requests and patches on the project's
+website at:
+  http://sourceforge.net/tracker/?group_id=202631

autogen.sh

@@ -0,0 +1,77 @@
+#! /bin/sh
+
+PKG_NAME="LitJSON"
+srcdir=${srcdir:-.}
+
+
+die ()
+{
+	echo "$@"
+	exit 1
+}
+
+
+want_glib_gettextize=false
+want_intltoolize=false
+want_libtoolize=false
+want_maintainer_mode=false
+
+configure_files=$(find $srcdir -name configure.ac -print -o -name configure.in -print)
+
+for configure_ac in $configure_files; do
+	if grep "^A[CM]_PROG_LIBTOOL" $configure_ac >/dev/null || \
+	   grep "^LT_INIT" $configure_ac >/dev/null; then
+		want_libtoolize=true
+	fi
+
+	if grep "^AM_GLIB_GNU_GETTEXT" $configure_ac >/dev/null; then
+		want_glib_gettextize=true
+	fi
+
+	if grep "^AC_PROG_INTLTOOL" $configure_ac >/dev/null || \
+	   grep "^IT_PROG_INTLTOOL" $configure_ac >/dev/null; then
+		want_intltoolize=true
+	fi
+
+	if grep "^AM_MAINTAINER_MODE" $configure_ac >/dev/null; then
+		want_maintainer_mode=true
+	fi
+done
+
+
+
+echo "Preparing $PKG_NAME .."
+
+if $want_libtoolize; then
+	echo "  running libtoolize .."
+	libtoolize --force --copy || die "libtoolize failed"
+fi
+
+if $want_glib_gettextize; then
+	echo "  running glib-gettextize .."
+	glib-gettextize --force --copy || die "glib-gettextize failed"
+fi
+
+if $want_intltoolize; then
+	echo "  running intltoolize .."
+	intltoolize --force --copy --automake || die "intltoolize failed"
+fi
+
+conf_opts=""
+if $want_maintainer_mode; then
+	conf_opts="--enable-maintainer-mode"
+fi
+
+echo "  running aclocal .."
+aclocal 2>/dev/null || die "aclocal failed"
+
+echo "  running autoconf .."
+autoconf 2>/dev/null || die "autoconf failed"
+
+echo "  running automake .."
+automake -a -c || die "automake failed"
+
+echo "  running configure .."
+${srcdir}/configure $conf_opts "$@" || die "the configure script failed"
+
+echo "Now type 'make' and 'make install' to install $PKG_NAME"

benchmarks/.gitignore

@@ -0,0 +1 @@
+*.dll