So this evening instead of reading history books...

[lizziec]

I did this.

I did all of it and it worked which is really cool :) Syntax hilighting in vim is lovely :)

Only problem with this is the problem I have with many things. Having done it and found it works I now want to know *what* I did (having copied the code) and *why* it works. I want to understand what I've done...

This can only be a bad thing :(

Anyway, while I'm here...rest of the day :) Helped the cs2er and then proceeded to do nothing with my day :) Had a nap that wasn't planned but welcome nonetheless :) :) Ate a whole 300g bar of chocolate and thus feel slightly sick... watched reach for the sky and had discussion about aeroplanes which was cool :D

hmm...notta lot else :) Sleepies soon methinks :D

Comments

[slimeypete.livejournal.com]

MSC
MSC
MSC


Seriously, I can see us swapping ;)


I love WWI history in particular.

[skeldof.livejournal.com]

Wrote a hello world app.

It worked cause it was a simple progam, with correct syntax :P

You created a class. Which contained only a single method. The method declared there is a special one. It is envoked whenever the class is called from the command line with the java command. You could have called that method anything, but only that main header would work.

System.out.println tells java to output the given string to STDOUT, and end it with a new line. You could have called .print() which wouldn't have terminated the line. System.out is the first time you come into contact with an output stream, but there's no need to worry about what an output stream is, just yet ;P

Stuff in ""'s are strings.

// Is a single line comment. Anything after // on a line is ignored by the compiler. For humans reading the code only

The stuff between /* and */ are multi line comments. Makes it easier than having to write // at the beginning of each line. By standard a * is added to each line to show it's still part of a multiline comment. Makes it easier to read in pants editors that don't syntax hilight. The * on each line are not required. Which is good for when you comment out large chunks of pants code ;D

/** notes that the multiline comment is a special one. It's called a javadoc comment. Instead of a programmer having to write seperate documentation the tool "javadoc" generates the documentation from those special comments in the code. Which is what you see when you read the javadoc API.

... I think that's enough. Any questions?

You still have bluej book. Although lots of people knock bluej, it's a good learning tool for getting head around Objects and how they interact with each other, using java as the example language. It doesn't teach you java, but Object Oriented programming concepts. You just happen to learn java as you go ;)