Welcome to the SWIG developer list

Just a quick message to welcome everyone to the Swig developer list.
The primary purpose of this list is to discuss issues related to the
Swig redevelopment effort, management of the CVS repository, and more
mundane issues related to creating the next release.  

Just so everyone is aware of everyone else, here are the current
members of this list:

   -  beazley <at> cs.uchicago.edu  (Dave)
      Given that it's my own personal disaster, I'm primarily working
      on migrating SWIG1.1 to use the new module system.

   -  djmitche <at> cs.uchicago.edu (Dustin Mitchell).
      Dustin is working on a number of issues related to the
      implementation of the new SWIG core--especially the details
      related to a number of internal data types.

   -  cldumitr <at> cs.uchicago.edu (Catalin Dumitrescu)
      Catalin is working on some very experimental work of creating
      compilers that utilize XML as data-interchange format and
      internal representation.

   -  iancooke <at> cs.uchicago.edu (Ian Cooke)
      Ian is working on an experimental new testing framework for
      Swig that will eventually replace the old "Tests" directory
      and be much more effective.

   -  bwking <at> midway.uchicago.edu (Bryan King)
      Bryan is working on a number of web-related projects related to
      the debugging and development of Swig.  At the moment, he is
      working on a browsing tool that makes it possible to navigate
      through the parser's internal parse trees.

   -  hbkovuk <at> midway.uchicago.edu (Hasan Baran Kovuk).
      Baran is also working on the web-based debugging tool for
      browsing through internal data structures.

   -  Loic Dachary (loic <at> senga.org)
      Loic has made a number of substantial modifications to the Perl5
      module.

   -  Harco.de.Hilster <at> ATComputing.nl (Harco de Hilster)
      Harco is the creator of the Swig Java module.

Now, with the introductions out of the way, the next few weeks are
probably going to be a little shaky as the project unders the
transition of having many more people working on it.  However, here
are the basic comments:

1.  First off, everything is checked in under the SWIG CVS
    repository. Everyone on this list should have write access to the
    repository. 

2.  The two directories of primary interest are probably the Source
    directory and the Doc directory.   Within the Source directory,
    there is a growing list of subdirectories corresponding to various
    subprojects.   The Doc directory contains various types of 
    documentation and whitepapers describing some of the projects.

3.  Even though there are number of subprojects going on, the primary
    configuration and build process always builds a "working" version
    of SWIG.  Currently, this version builds a hybrid system based on
    the SWIG1.1 core with a preprocessor added to it.   Over time, I
    expect to deprecate this code based and replace it with something
    else.  However, in the meantime, I consider it to be important
    that we at least have something that works.

4.  Experimental versions of SWIG should be built by adding different
    Makefile targets to the top-level Makefile.  The only such target
    right now is 'make experiment' that builds an experimental version
    based on an alternative parser and parse-tree representation for
    instance.

I'll have more to say at a later date.  However, in the meantime I'm
working on a few documentation issues.  In the meantime, I'm hoping
that everyone can use this list to discuss various technical issues
and other matters related to the system.

Cheers,

Dave