Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #21159

Re: (golf-ish) Conditional object property access

Show all headers | View raw

Ben Bacarisse wrote:

> Thomas 'PointedEars' Lahn <PointedEars@web.de> writes:
>> Ben Bacarisse wrote:
>>> If HAS returns o.p when o.hasOwnProperty('p'), then you can avoid the
>>> conditional
>>> 
>>>   HAS(o, 'p') || <EXPR>
>>
>> Incorrect.  There is a difference between an object having a property and
>> converting the result of a property access to Boolean.  Assuming you
>> meant
>>
>>   function HAS (o, p)
>>   {
>>     if (o.hasOwnProperty(p)) return o[p];
>>   }
>>
>> (where “HAS” is a very unwise identifier), if the value of o[p] was a
>> false- value, the result of
>>
>>   HAS(o, 'p') || <EXPR>
>>
>> would be
>>
>>   <EXPR>
> 
> Yes, good point.  I've used something similar, but in situations where
> this problem would be unlikely.  I was too hasty, though I suppose it's
> possible that || works in all the OP's use cases.

I do not think there is a use-case here.  That is the very nature of code-
golfing, because it is more play than work: trying to find the shortest 
equivalent expression, however unreadable, to solve a *theoretical* problem.  
You would never used golfed code in production: it is probably inefficient, 
likely error-prone, and definitely hard to maintain.
 
>>> Anything that uses functions to wrap EXPR for delayed execution suffers
>>> from the fact the ECMAScript uses such a long keyword, and that the
>>> syntax requires empty parentheses.  (I take it that one of the rules of
>>> this golf game is that the expression should be short.)
>>
>> Harmony (ECMAScript Edition 6) is going to fix that with foo(bar => baz):
>>
>> <http://wiki.ecmascript.org/doku.php?id=harmony:arrow_function_syntax>
> 
> Nice.  The return is no longer needed in simple cases too.  It's always
> seemed to me that the early designers never expected the wide use that
> function expressions would get.

ISTM that this particular syntax for lambda expressions was borrowed from 
C#, which in turn might have shortened that of Python.  I learned it when I 
first used LINQ extension methods about a year ago.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

(golf-ish) Conditional object property access kj <no.email@please.post> - 2013-09-02 20:23 +0000
  Re: (golf-ish) Conditional object property access Ben Bacarisse <ben.usenet@bsb.me.uk> - 2013-09-02 21:52 +0100
    Re: (golf-ish) Conditional object property access Stefan Weiss <krewecherl@gmail.com> - 2013-09-02 23:11 +0200
    Re: (golf-ish) Conditional object property access Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-09-03 00:03 +0200
      Re: (golf-ish) Conditional object property access Ben Bacarisse <ben.usenet@bsb.me.uk> - 2013-09-02 23:19 +0100
        Re: (golf-ish) Conditional object property access Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-09-03 01:59 +0200
  Re: (golf-ish) Conditional object property access Stefan Weiss <krewecherl@gmail.com> - 2013-09-02 23:10 +0200

csiph-web