Ruby parens-free function calls [was Re: Accessing parent objects]

Rick Johnson rantingrickjohnson at gmail.com
Sun Mar 25 22:16:12 EDT 2018


On Sunday, March 25, 2018 at 5:57:28 PM UTC-5, Steven D'Aprano wrote:

> [supposed "fix" to the sample script snipped]
>
> You know Rick, every time I start to think that talking to
> you like an adult might result in a productive and
> intelligent conversation, you pull a stunt like this.  Once
> I recover from laughing at your inability to read a simple
> eight line Ruby script, and then laughing even harder at
> your inability to tell the difference between a string in
> Ruby and an actual function call, I *might* come back and
> read the rest of your post.

Q1: Do my modifications throw an error???

If so, then provide this group with the exception message
and you shall be redeemed.

Q2: Did my "fix" fail to meet the highly generalized
qualification of "un-obfuscating the code"???

If not, then explain to this group exactly how i failed.

Steven, your highly competitive nature is apparent
to any and all who frequent this group. And i'm sure i speak
for everyone here when i say that we all appreciate the vast
wealth of knowledge you bring to the table. But this time
you have allowed your emotions to get the better of you, and
now your friendly barbs have become purposeful
misrepresentations.

Listen, if i make a false statement or give bad advice on
this list, then i _want_ someone to call me on it. But for
you to cast accusations without providing any evidence to
support those accusations, is beneath the dignity of this
mailing list. I stand behind my "code fix" and i confidently
claim that not only does it meet the requirements, it also
runs without error. And if you disagree with my claim, then
bring forth your evidence.



More information about the Python-list mailing list