From paul@inet.co.za  Mon May 15 11:03:59 2000
Received: from exchange_rbk02.inet.co.za (exchange-rbk02.inet.co.za [196.38.91.22])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id LAA28940;
	Mon, 15 May 2000 11:03:52 +0200 (MET DST)
Received: from pdev.inet.co.za ([196.14.60.35]) by exchange_rbk02.inet.co.za with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K81Z33HB; Mon, 15 May 2000 11:05:22 +0200
Date: Mon, 15 May 2000 12:53:21 +0200 (GMT+0200)
From: Paul Sephton <paul@inet.co.za>
To: Jan Wielemaker <jan@swi.psy.uva.nl>
cc: Paul Singleton <p.singleton@keele.ac.uk>, prolog@swi.psy.uva.nl
Subject: Re: String Representation
In-Reply-To: <00051510355502.06671@gollem>
Message-ID: <Pine.LNX.3.91.1000515124536.19575A-100000@pdev.inet.co.za>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Thanks, Jan- That helps immensely.  There really isn't a good case for 
strings at all (as a seperate type from atoms) under those circumstances, 
is there?

I suppose enumerating the atom table occurs infrequently enough not to be 
an issue.  What are the overheads associated with storing lists of 
characters or lists of single character atoms?  Is this a byte per 
character?  I don't suppose it could be since the hash key on an atom 
must be larger- or possibly you use the first 256 hash keys for 
storing characters and simply use offsets?

Again, thank you. Understanding those details helps toward efficient code.

Regards
Paul
_____________________________________________________________________________
Paul Sephton (paul@inet.co.za)                               INET Development
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ever wondered if jumping out of the frying pan might actually be refreshing?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

