From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <chris@the-brannons.com>
Received: from localhost (unknown [IPv6:2602:b8:6489:8a00::35bb:7ca9])
 by hurricane.the-brannons.com (Postfix) with ESMTPSA id 85D5877C83
 for <edbrowse-dev@lists.the-brannons.com>;
 Sun, 23 Jul 2017 18:04:34 -0700 (PDT)
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
References: <20170623205238.eklhad@comcast.net>
Message-ID: <87tw22d4r4.fsf@the-brannons.com>
Date: Sun, 23 Jul 2017 18:04:47 -0700
In-Reply-To: <20170623205238.eklhad@comcast.net> (Karl Dahlke's message of
 "Sun, 23 Jul 2017 20:52:38 -0400")
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Edbrowse-dev] Object identifiers
X-BeenThere: edbrowse-dev@lists.the-brannons.com
X-Mailman-Version: 2.1.24
Precedence: list
List-Id: Edbrowse Development List <edbrowse-dev.lists.the-brannons.com>
List-Unsubscribe: <http://lists.the-brannons.com/mailman/options/edbrowse-dev>, 
 <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=unsubscribe>
List-Archive: <http://lists.the-brannons.com/mailman/private/edbrowse-dev/>
List-Post: <mailto:edbrowse-dev@lists.the-brannons.com>
List-Help: <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=help>
List-Subscribe: <http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev>, 
 <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 01:04:34 -0000

Karl Dahlke <eklhad@comcast.net> writes:

> So I'm thinking instead, why don't we create our own IDs.
> Just a sequence number that we put on every object we care about, and an array to map back from sequence number to the object.
> A bit of overhead, but no crashes if we accidentally reference an object that is gone, and no ambiguity - one object per id.

I like this.  It is the safe approach.  How will objects in the object
ID mapping table be freed?

-- Chris