Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!maverick.ksu.ksu.edu!uafhp!jcs
From: jcs@uafhp.uark.edu (James Sullins)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Program to update SIMIBM.IDX (Simtel20 index) file
Summary: Two good reasons NOT to use diff/patch to update SIMIBM.IDX
Keywords: simmod,simtel,simibm.idx,index,update
Message-ID: <5114@uafhp.uark.edu>
Date: 18 Aug 90 10:48:11 GMT
References: <5098@uafhp.uark.edu> <13925@yunexus.YorkU.CA>
Organization: College of Engineering, University of Arkansas, Fayetteville
Lines: 38

In article <13925@yunexus.YorkU.CA>, rreiner@yunexus.YorkU.CA (Richard Reiner) writes:
> 
> I agree that distributing deltas for the SIMIBM.IDX file is a good idea;
> however, let's stick to the standard tools: diff and patch.  There's
> no good reason to invent and install a new mechanism for a task which
> is already handled very well by existing tools.
> 
> --richard


I feel there are two very good reasons for using my method instead
of diff/patch for updating the SIMIBM.IDX file:

	1) SPEED.

           The SIMMOD program is approx. 2 times faster than PATCH.
           The IDXMOD program is approx. 3 times faster than DIFF.
           These factors make a considerable difference on my PC.

        2) FILE FORMAT.

	   The files (additions/deletions) used by my programs
	   maintain the same format as the SIMIBM.IDX file.

	   This allows you to run the "additions" file through
	   SIMCVT (or similar program) to quickly find out what
           has been added.

           This also makes it possible to easily "merge" several
           "diff" files into one so that you can apply several
           "patches" at once without the need to recreate each
           intermediate index file.

BTW, the IDXMOD program is the program used to create the additions
and deletions files.

-----
James Sullins - jcs@uafhp.uark.edu