From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34441-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 19205 invoked by alias); 31 Jan 2015 03:22:24 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 34441
Received: (qmail 29219 invoked from network); 31 Jan 2015 03:22:12 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=B94OC1pJ c=1 sm=1 tr=0	a=FT8er97JFeGWzr5TCOCO5w==:117
 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8	a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10
 a=YNv0rlydsVwA:10	a=n9sd6i70tcVWT3Ux4VMA:9 a=CjuIK1q_8ugA:10
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <150130192144.ZM17686@torch.brasslantern.com>
Date: Fri, 30 Jan 2015 19:21:44 -0800
In-reply-to: <20150130085949.4d44007d@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
 "Re: Anyone want to help make zsh/db/gdbm work?" (Jan 30,  8:59am)
References: <150122211942.ZM28918@torch.brasslantern.com>
	<CAECNH1RmrF9+w86zPxoiG=TM9j_0rdeeW9LV+9Qp0ksQ7LyJVg@mail.gmail.com>
	<20150129204658.4a800bcb@ntlworld.com>
	<150129140625.ZM14730@torch.brasslantern.com>
	<20150130085949.4d44007d@pwslap01u.europe.root.pri>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: Anyone want to help make zsh/db/gdbm work?
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

Ok, some other thoughts on this ...

ztie should have a flag (probably -r) to open the database read-only.
(I've already implemented this, don't go running off to do it.)

However, this raises the question of whether the resulting parameter
should also be readonly.

If it is, then it can't be unset, which currently means it also can't
be zuntied.  On the other hand, even read-only locals disappear when
they go out of scope.

However, this makes me wonder whether it's correct for zuntie to unset
the parameter.  Maybe an explicit zuntie should just convert the param
into an ordinary hash, closing the database file from under it?  (This
I have not implemented yet.)

Thoughts?