On 13.12.18 11:12, Josef Reidinger wrote:
Well, at least ruby syntax check returns you warning (and of course rubocop
also). Maybe we can simply check for warning in this check in travis? As we
already did syntax check, but it is not hard failure because meta programming
can potentially allows you to survive this situation.
try it yourself:
ruby -wc weird.rb # w is warning and c is syntax check
/tmp/weird.rb:17: warning: ambiguous first argument; put parentheses or a space
even after `+' operator
Syntax OK
Yes.
That warning is COMPLETELY USELESS. It does not answer any question, it just
raises questions.
In that regard, Ruby is even worse than gcc was 15 years ago. The gcc people
at least in the course of those decades managed to issue well understandable
error messages.
So we'll only have to wait for another 15 years or so for Ruby to catch up.
Well - wait; Ruby is indeed not that new:
https://en.wikipedia.org/wiki/Ruby_(programming_language)
"First appeared: 1995; 23 years ago"
One would think that this is plenty of time to come up with some rudimentary
sanity checks and error messages that can be understood by the average developer.
So, please, let's not make any more excuses for something that appears to be
fundamentally broken. It's the mindset of those people that makes it worse,
and the tendency to find apologies for something that is clearly broken is
part of it.
Kind regards
--
Stefan Hundhammer <[email protected]>
YaST Developer
SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
