51–60 of 116 posts
Earlier quoted context omitted.
The greatest difficulty with code is not in writing it but in reading it.
if/unless is pretty common in natural language for good reason. I find it far more readable than prefix, block-form if for the simple case of one-line results with no alternative branch.,
def do_stuff()
return unless stuff_enabled?
...
endAll linters and C compilers emit a warning when an assignment is made in a condition. There are zero reasons to use that ugly and unnatural Yoda notation in 2019.
I think this is reasonable readable: while ((status = systemcall(...)) != SUCCESS) { do something with status; } Leave a comment there explaining the assignment. Likewise: if ((status = systemcall(...)) != SUCCESS) goto error; Or something like that. I don't understand the hate, just make sure it's obvious what you're doing.
while(status != SUCCESS) {
status = syscall(...);
// do something with status
}One example of a large code base that uses this is WordPress (PHP).
Earlier quoted context omitted.
I think this is reasonable readable: while ((status = systemcall(...)) != SUCCESS) { do something with status; } Leave a comment there explaining the assignment. Likewise: if ((status = systemcall(...)) != SUCCESS) goto error; Or something like that. I don't understand the hate, just make sure it's obvious what you're doing.
This would achieve the same but is far more readable: while(status != SUCCESS) { status = syscall(...); // do something with status }
All linters and C compilers emit a warning when an assignment is made in a condition. There are zero reasons to use that ugly and unnatural Yoda notation in 2019.
I think this is reasonable readable: while ((status = systemcall(...)) != SUCCESS) { do something with status; } Leave a comment there explaining the assignment. Likewise: if ((status = systemcall(...)) != SUCCESS) goto error; Or something like that. I don't understand the hate, just make sure it's obvious what you're doing.
int c;
while((c = getopt(argc, argv, argstr)) >= 0) {...}
Is there a shorter way of saying, "the wrong solution to the right problem"?
One example of a large code base that uses this is WordPress (PHP).
Good job duplicating that second paragraph of the linked article.
EDIT: to be fair, this sentence was added today [1]. Not sure if it would have been there when I opened the tab earlier.
[1] https://en.wikipedia.org/w/index.php?title=Yoda_conditions&t...
All linters and C compilers emit a warning when an assignment is made in a condition. There are zero reasons to use that ugly and unnatural Yoda notation in 2019.
I think this is reasonable readable: while ((status = systemcall(...)) != SUCCESS) { do something with status; } Leave a comment there explaining the assignment. Likewise: if ((status = systemcall(...)) != SUCCESS) goto error; Or something like that. I don't understand the hate, just make sure it's obvious what you're doing.
But enabling it on the language level brings a large amount of risk and complexity just for what amounts to a micro-optimization.
Am I sure pretty any that linter warning a throw can of instead breaking flow the both of reading writing and.
Despite the name, it isn't referring to Yoda's grammar form, it's just reversing things around "and" and "or". If you really have a problem telling that "x == y" is the same as "y == x" I suggest coming to a deeper, more complete understanding of the equality operator as a commutative operator where the order doesn't matter rather than thinking of it as "variable is? value", as so many students clearly pick up accide…
More often than not, the first solution to a problem isn't the best, but the best solution would take a lot of tooling fixes.
The Yoda condition trick is a relic of the past, well past its usefulness and best left in its grave alongside Hungarian notation, macros for "inlining", #include "blah.c", goto, etc.