View Full Version : The Horror....

01-11-2005, 12:48 AM
I was in the computer lab at my school today...and being the nerd that I am, I noticed Dev C++, and opened it up.
Clicked through to create a new source file.

:eek: I was shocked. :eek:

Warning, some may have difficulty with the next line of code. Viewer Discretion advised.
I present to you the first line in this nearly blank source file:

#include <iostream.h>

I kid you not, this is what could-be programmers are being taught at my high school.

I was horrified!!! (Thankfully I'm not doing any programming at the school! That was a close call!)

01-11-2005, 02:27 AM
hey, "#include" is a perfectly appropriate pre-processor directive :)

01-11-2005, 07:49 AM
I'm surprised. Is it a really old version of DevC++? I have it on my home computer but I really just use it for its copy of gcc and I never use wizards to generate code so I wouldn't have seen that.

01-11-2005, 07:56 AM
Change schools immediately, and alert the police of your observations as soon as possible!

01-11-2005, 08:19 AM
I was on the network drive at this tech school I went to...got into some of the tests or test preparation assignments, unsure which they were.

Anyways near the end of the course(they had it all divided up neatly in timeframes by folder) they still had them working on loops, in a C++ course. And almost everything I saw was void main. :(

01-11-2005, 08:28 AM
:( Well at least it wasn't a professional software class

01-11-2005, 11:15 AM
My school is too dumb to teach c++. They have an advanced computer class 2 but its all web. Even though I may not be very skilled with html and whatnot. I assure you I know 3 times as much as any of those kids. I can't be on the web team because I have to pass the other comp classes. I'm not terribly good at typing and we stupid crap in excel and word. After looking at the source code of our web site I have concluded they copy and pasted half of it from other web sites.

01-11-2005, 04:50 PM
oh ya, lets not forget the end of that program as well...it was equally horrifying...

take a guess...system(); Can YOU Guess what is inside? :P

01-11-2005, 06:24 PM
take a guess...system(); Can YOU Guess what is inside? :P
del Q R c:\windows? :P

01-11-2005, 07:08 PM

Duh, how else are you supposed to quit the program?

01-11-2005, 07:36 PM
I always thought you quit the program by clicking the [x] in the corner, and then clicking Yes on the dialog box :P

01-11-2005, 10:15 PM
:D :D I like gcn's method :D :D

Zach L.
01-11-2005, 10:19 PM
Pulling the power cord works too (or the battery as applicable).

01-11-2005, 11:03 PM
You do realize, there's a power button at the front and a power switcheroo at the back. They offer better compatibility with the latest MS OS.

Zach L.
01-11-2005, 11:20 PM
But less fun. :D

01-12-2005, 07:59 AM
return 0 always works for me...

01-12-2005, 04:52 PM
>>But less fun.
Ah, yes - the butter of life. I personally find it satisfying to unscrew the case and short the motherboard in a strategic location. I've located several hotspots that work a charm, and even managed on one occasion to close just the target window :p

Now, the challenge is to build a robotic arm that attaches universally to any case, and write a platform- and case-independent program that causes the arm to reach over, unscrew the case, locate an appropriate shorting point, and then close the application via hardware. Bonus marks if the arm puts the computer back together afterward :D

Zach L.
01-12-2005, 05:00 PM
Nah... Thermite. :D

01-12-2005, 05:12 PM
A robotic arm that makes, places and ignites thermite :D

Zach L.
01-12-2005, 05:13 PM
Okay... That is probably wise.

01-12-2005, 05:16 PM
I'll leave beta testing to you.

01-12-2005, 06:38 PM
Must be an old version of Dev-C++. Mine uses iostream but still uses system("PAUSE"). High schools seem to be notorious for using out of date software. Usually because of a budget situation but in this case since Dev-C++ is free there is no excuse, but it still doesn't surprise me.

01-12-2005, 07:50 PM
You are all forgetting the bat/hammer method which brings the added security of not only quitting your program, but also making sure it will never start again!;)

01-13-2005, 02:45 PM
Did you try opening the window, grabbing the computer, stick it out of the window and release it? That might stop the program [especially if you're on the 3d floor or so]. If that didn't help, buy a new computer.

Zach L.
01-13-2005, 02:57 PM
If that didn't help, buy a new computer.
Even if it did, you probably ought to get a new one. :p
... or perhaps, especially if it did. :)

01-13-2005, 03:02 PM
Even if it did, you probably ought to get a new one. :p
... or perhaps, especially if it did. :)
Oh yeah, minor detail.

I hope nobody followed my advice...

Taking a hammer and hitting on it (the computer, not the monitor) is much more efficient and faster (and might not entirely molest your PC).

01-13-2005, 06:46 PM
>>If that didn't help, buy a new computer.
Nah, it's just a bug in Windows XP. MS fixed it in their latest update, so the computer should die properly now when you destroy it ;)