Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: setup - parsing code
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Sat, 4 May 2002 14:38:50 +1000
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5FB6@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Cygwin-Apps" <cygwin-apps AT sources DOT redhat DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g444csg18790

If you want to edit the parsing code, I've just restructured it.

The parser is in inilex.l and iniparse.y as previously.

Rather than iniparse.y also knowing what objects and classes to use to
build the in memory use of the ini file, it uses an IniDBBuilder to
create that representation. 

Currently there are two IniDBBuilders - the base class, and one with the
same behaviour the old code has - that is it merges the data into the
packagedb.

The reason for this is to allow other uses of the parser - such as the
inilinter I'm working on, or a mirroring tool that really doesn't care
what packages are on the system.

Rob