From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Object identifiers
Date: Sun, 23 Jul 2017 18:04:47 -0700 [thread overview]
Message-ID: <87tw22d4r4.fsf@the-brannons.com> (raw)
In-Reply-To: <20170623205238.eklhad@comcast.net> (Karl Dahlke's message of "Sun, 23 Jul 2017 20:52:38 -0400")
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
next prev parent reply other threads:[~2017-07-24 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 0:52 Karl Dahlke
2017-07-24 1:04 ` Chris Brannon [this message]
2017-07-24 5:25 ` Dominique Martinet
2017-07-24 6:43 ` Karl Dahlke
2017-07-24 7:49 ` Dominique Martinet
2017-07-24 7:03 ` Karl Dahlke
2017-07-24 5:43 ` Robert Ransom
2017-07-24 17:45 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tw22d4r4.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).