[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#802595: ITP: node-defined -- return the first argument that is `!== undefined`

Ross Gammon wrote:
>Package: wnpp
>Severity: wishlist
>Owner: Ross Gammon <rossgammon@mail.dk>
>X-Debbugs-CC: debian-devel@lists.debian.org
>* Package name    : node-defined
>   Version         : 1.0.0
>   Upstream Author : James Halliday <mail@substack.net> 
>* URL             : https://github.com/substack/defined
>* License         : Expat
>   Programming Lang: JavaScript
>   Description     : return the first argument that is `!== undefined`
>  Most of the time when you chain together ||s, you actually just want the
>  first item that is not undefined, not the first non-falsy item.
>  .
>  This module is like the defined-or (//) operator in perl 5.10+.
>  .
>  Node.js is an event-based server-side JavaScript engine.
>This package is required for tape 
>(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798278) and will be 
>maintained within the Debian Javascript Team.

YA tiny Javascript "library" containing 3 lines of utterly trivial
code. :-(

I appreciate you're just following through a dependency chain from
upstream for tape, but please push back on upstream and ask them why
they're doing this kind of ridiculous split-up. Code re-use in general
is a good plan, but not at the level of every trivial helper function
being split out into its own library!

Steve McIntyre, Cambridge, UK.                                steve@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Reply to: