On Wed, Dec 2, 2015 at 6:44 PM, ermouth <ermo...@gmail.com> wrote: > Ain‘t it all too stressful? > > Approach will make _all_ existing code broken, that will, in turn, > effectively deny upgrade for most of users.
Deprecate != remove. Both approaches may co-exist for some time till we find a way how to gracefully upgrade the code during yet another BC release. The drawback of such upgrade will be all views rebuild, suddenly. > Think old and new approaches better co-exist during several subversions. > Note, that co-existanse makes passing ctx via 1st arg impossible. It is not possible to check how many arguments functions accepts? I thought about this way to deal with this problem. > As for me, I‘d prefer to have emit and co as `this` childs. Like > this._emit, this._send, this._getRow and so on. Since properties with > leading _ can not exist in ddoc, referenced by `this`, we can extend `this` > free. > > Actually, we must have several shallow copies of ddoc, each extended with > own set of underscored methods. Each calll to QS function performed using > .apply with and appropriate shallow copy. How this._* will be better than global context? Just curious. -- ,,,^..^,,,
