Message-ID: <20010213155608.236.qmail@lauras.lt>
From: "Laurynas Biveinis" <lauras AT softhome DOT net>
Date: Tue, 13 Feb 2001 17:56:08 +0200
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: PATCH: new djtar option
Mail-Followup-To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	djgpp-workers AT delorie DOT com
References: <20010212200601 DOT 786 DOT qmail AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010213090508 DOT 25782A AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
In-Reply-To: <Pine.SUN.3.91.1010213090508.25782A@is>; from eliz@is.elta.co.il on Tue, Feb 13, 2001 at 09:08:08AM +0200
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Also, at least for skipping directories, you could use the same data 
> structure used by djtar for mapping file names: there's already a 
> provision there to skip files and directories.  It would make the code 
> less complicated.

But hash tables deal with full filenames only; I put a prefix 
'gcc-3.0/libjava' in it, but 'gcc-3.0/libjava/foo' generates a different
hash code, and the match isn't detected. Maybe in this case my linked
lists would make the code less complicated?

Laurynas