I'd steer clear of HTML. It does not teach you anything about programming really, it is mearly a document formatting tool (and arguably LaTeX would be better to learn if that was your goal).
furry muff
I was just thinking of a simple language to start with.
I remember being overwhelmed by C when i started learning it. Pointers, arrays etc. I hated it some much i've never used it since my exam in it.
The only document formatting language I consider to be a programming language is PostScript. But I'm not sure learning that teaches much about general purpose programming!
furry muff
I was just thinking of a simple language to start with.
I remember being overwhelmed by C when i started learning it. Pointers, arrays etc. I hated it some much i've never used it since my exam in it.
My response seemed to get lost at the end of the first page, but I was at least trying to be civil about it. =) I think HTML is nice because you can very quickly make changes and see the results, which can be rewarding, but i've never taken what I've learned from HTML and applied it to programming elsewhere. It's certainly not a waste, especially in this day-in-age in which so much is being pushed to browser-based applications. HTML has become the front-end for a lot of very complex applications.
-Lee
P.S. I guess i started in with "turing completeness"... I guess we computer science folk can be a bit uppity and droll at times. I am a language nerd, and when I think "general purpose" I just say "Turing complete".
P.P.S. Since you brought up Gödel, it reminded me of this: http://xkcd.com/468/
I didn't say it did . I said "it doesn't teach you anything about programming really" and then went on to state that if your goal was to learn a document formatting tool then LaTeX would be a better bet than HTML.
Maybe I should have left the really off to sound more decisive on that statement.
Keytachi, I don't see why you need to learn any languages right now. Go run around outside in the sunshine. This is the last chance for you to do that sort of thing for years.
Sun is bad for future programmers - you must build up an immunity to sunlight so you can work for weeks in your curtain drawn hovel
Sun is bad for future programmers - you must build up an immunity to sunlight so you can work for weeks in your curtain drawn hovel
Keytachi, I don't see why you need to learn any languages right now. Go run around outside in the sunshine. This is the last chance for you to do that sort of thing for years.
I like my hovel .
Since we're so far OT by now anyway, you got started in these forums the same way the OP is. When does your first term at university start? With our help do you feel you've gotten yourself far enough ahead to embarrass your peers?
-Lee
I still manage to make a tit out of myself with spectacularly simple mistakes though .
Or the infamous = instead of == . That's always a fun one.
boolean enterIf=true;
if(enterIf) {
System.out.println("Entered 'then' section");
} else {
System.out.println("Entered 'else' section");
}
if(enterIf == true)
if(enterIf = true)
if(NULL == someVar)
if(someVar == NULL)
Do you guys use the method like this:
Code:if(NULL == someVar)
or this:
Code:if(someVar == NULL)
?
The first gives a decent compiler error but it is not as easy to read if you ask me. Maybe it is just getting into the habit of using it. I guess I should try.
Or the infamous = instead of == . That's always a fun one.
Or the infamous = instead of == . That's always a fun one.
I injected this very bug into some production C++ code at work very recently, as part of some complicated conditional clause. The ill effect only surfaced some of the time due to the short circuiting of the logical || operator within said conditional clause.
Indeed, spending the two hours or so to track it down (down some blind alleys too) was a hoot.
But did you find and fix any other bugs in the process?
-Lee