Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <63953CC0-7576-4A77-8284-DFA6529E6FF1@apache.org>
References: 
 <CAHdjipKj2kJD9MFE_tXwV8Wyt9CFtVOBnx31-v=z4jTs6V1img@mail.gmail.com>
	<63953CC0-7576-4A77-8284-DFA6529E6FF1@apache.org>
Date: Wed, 2 Dec 2015 15:42:37 +0300
Message-ID: 
 <CAHdjipKFT9BpbS_SwzK2bxr-hi+81Y44crNMn_7DfQvXOccncQ@mail.gmail.com>
Subject: Re: [PROPOSAL] Deprecate global functions in query server
From: Alexander Shorin <kxepal@gmail.com>
To: couchapp@couchdb.apache.org
Cc: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Garren,

On Wed, Dec 2, 2015 at 3:35 PM, Garren Smith <garren@apache.org> wrote:
>
> This is an interesting idea. I think passing the emit function in is a go=
od idea and might make somethings easier in PouchDB. I would rather a  map =
function looked something like this
>
> function (doc, emit) {
>
> }

That's nice, but won't work: map function has access to a lot of other
global functions we provide, so you'll end with signature of 7
arguments.  I don't think there is any reason to fix this problem by a
half. Just fix all globals or no one.

> I don=E2=80=99t like the idea of passing a userCtx object. That feels ove=
rly bulky. Things like JSON/require are global variables in Node.js or the =
browser so my feeling is to follow their lead on those.

ctx referenced not to userCtx, but a generic context object that hold
all the global function and objects we provide now. These are listed
in reference on documentation. May be we can find a better name to not
cause confusion. funcs? env? Suggestions welcome (:

--
,,,^..^,,,