|
End users typically don’t understand and misuse and abuse technical terms. A little knowledge is a very dangerous thing.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
It's like "OH MY GOD! THE NUCLEAR REACTOR'S GONE CRITICAL!!!"
Um, yeah. That's when it produces the electricity.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Off Topic my favourite goto label was hell, saw it in a code review
//error handle
goto HELL;
still makes me chuckle!
|
|
|
|
|
Reminds me of CHILL, the ITU standard language for programming digital phohe switches. The keyword EVER was defined for the FOR loop, so to set up an infinite loop (which makes perfect sense in telephone switch software), you wrote FOR EVER ...
|
|
|
|
|
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic.
Still, one tech writer writes an article calling a simple op-code "evil" and 30 years (or thereabouts) later we still think anyone using a GOTO command is a programming idiot.
To this day, all tech writers must earn my respect before I trust what they write.
modified 17-Sep-13 8:14am.
|
|
|
|
|
R_L_H wrote: Still, one tech writer writes an article calling a simple op-code "evil" and 30 years (or thereabouts) later we still think anyone using a GOTO command is a programming idiot. If GOTO is bad, why do all processors have them (jumps)? I always snarled whenever some idiot would proclaim that if it were in their power they would eliminate assembly language.
R_L_H wrote:
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic. |
I agree, I learned to program before structured code and GOTOs were necessary and I certainly spent time digging through code that loop-de-looped because either the programmer thought they were clever, didn't want to restructure the code, or were incompentent to begin with. See this[^], actual production code from a commercial database program from the 80's. Needless to say, we trashed that code as soon as we found it. The original programmer thought he was genius as evidenced by the thousands he was making a month in royalties.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
R_L_H wrote: GOTO was never the problem-- prevalent abuse of the keyword and poor code
structure was the epidemic No tech writer ever told me it was evil. Nor did common knowledge. I know from personal, painful, first-hand experience. Things got a lot more manageable when function calls were invented, but by then GOTO had its bad reputation. And back before function calls, it wasn't abuse -- it was the only way to write a program.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
I actually thought of a valid use for GOTO the other day - transliterating C64 code.
|
|
|
|
|
This is what I got from Newegg:
Motherboard: Asus Maximus VI Hero
CPU: Intel i7-4770K 3.5 GHz
Memory: Trident X series DDR3, 2 x 8 GB
Graphics: Asus GTX 660 Ti 2GB
System drive: Samsung 840 Pro series 256 GB SSD
Data drive: Seagate Barracuda 2 TB 7200 with 64 MB cache
OS: Windows 7 64-bit
Case: Rosewill R5 mid tower with plenty of fans and a very roomy interior
Power: Rosewill Lighting-1000
I had forgotten to get a CD rom, so I picked up an LG BR-R / DVD-RW at Fry's, along with some new Bose speakers (no sub-woofer this time: the people in the apartment below me have been complaining.) Kept my 1920 × 1080 HD screen, which I bought less than a year ago. Everything running like a dream: my "Windows Experience Score" is 7.8 (and that, apparently, only because the CPU has only 8 processors; everything else is 7.9.)
I do have a question, though: the case has two fans in the front, but the MB has only cluster of pins for plugging in the front fan (there is one other fan in the back, which is plugged in fine.) Should I look for a splitter cable that will let me connect both, or will one fan be fine?
|
|
|
|
|
No SSD?
/ravi
|
|
|
|
|
Lost your glasses? It says SSD on the line above the HDD!
|
|
|
|
|
DaveAuld wrote: Lost your glasses? What gave that away?
/ravi
|
|
|
|
|
The system drive is a 256 GB SSD.
|
|
|
|
|
Yes. And I'm as blind as a bat.
/ravi
|
|
|
|
|
Nice build.
On the fan front:
One will probably be fine, although it depends on what the outlet fan is doing. Monitor the temperatures over time and see how things are, particularly once you load up the GPU.
On your WEI, mines a 7.9 and that is because of the SSD. the CPU/Ram get 8, the Graphics get 8.2 You can read about mine here: Major Component Upgrades with a twist, benchmarks and all![^]
Cheers,
|
|
|
|
|
Wow, I thought 7.9 was the current high benchmark. I haven't overclocked anything (yet), maybe that's my problem
|
|
|
|
|
IIRC, 7.9 was the cap at the release of Windows 7, they upped the limit at some point.
I really need an SSD, it's holding my score back.
|
|
|
|
|
Nice machine. Apparently you can double your ssd's speed if you raid it with an identical one. But that's only worth it if you won the lotto and have the bucks to throw away.
Enjoy.
|
|
|
|
|
Sounds like a slick rig. How much did that put you out?
|
|
|
|
|
Total cost was just under 2000 USD, which includes Office 2010 Pro. More than I liked spending, but my current rig was showing its age (5.5 years old and in a case that's a bit too small and thus difficult to keep cool.) Building it myself saved at least $500 and it doesn't have any bloatware installed.
|
|
|
|
|
Gregory.Gadow wrote: and it doesn't have any bloatware installed
Yet.
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre.
Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
|
|
|
|
|
Well, at least I didn't have to spend two hours trying to uproot adware, demos and various other crap.
|
|
|
|
|
Only two hours? I take it you've never bought a computer with Symantec pre-installed?
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre.
Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
|
|
|
|
|
OriginalGriff wrote: Only two hours? I take it you've never bought a computer with Symantec
pre-installed?
Now that you mention it, I've never had that... um... privilege.
|
|
|
|
|
It is apparently possible to remove Symantec in less than a day, but I'd imaging you would need a Special Tool[^]
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre.
Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
|
|
|
|