void foo()
{
String result;
if (...)
result = a;
else (...)
result = b;
else (...)
result = c;
return result;
}
or
void foo()
{
String result;
if (...)
return a;
else (...)
return b;
else (...)
return c;
}
Both are common, but compile to different code. Do you code to 'a procedure should live on a page'? How about 'a procedure should have a purpose'? Return errors or throw exceptions? Return values or modified arguments? Kitchen sink constructors? Getters & setters or fluent builders? There's seven variables without stopping to think, dividing coders 128 ways, and I'm sure you could find another dozen or so, taking it to one-in-a-million level. There's no need to obfuscate...
When you prop up companies and banks that "are too big to fail" it's not really a free market.
It's not really capitalism. The government has interfered in the ownership model, not in the price setting for goods and services.
In fact, the sweet corn market where I live has a bubble every damned year - supply peaks in spring/summer and everyone is selling corn cheap then
... supply plummets and the price goes up
That's not a bubble, it's a glut; a bubble involves speculation.
The Republicans only pwn a single news channel.
FTFY.
How else do you make the trains run on time...?
You adjust the timetable to match reality. The trains aren't any faster, but the timetable no longer lies.
The moon is made of green cheese. -- John Heywood
