Java multiple classes

http://www.youtube.com/watch?v=XqTg2buXS5o&feature=player_profilepage#t=179s

     tuna tunaObject = new tuna();


Someone care to explain why you need to type "tuna" at the beginning and "tuna()" at the end if you already stated that you're going to use the tuna class at the beggining?
I think I understand the "tunaObject" is(the variable to which you will assign the new class in the main class, right?), but the "new" is still kind of ... I don't understand it either...
:/

>>39
More to the point, the reference variable tunaObject can now reference an instance of the Tuna class.

>>40
This is only useful for destroying braincells.

Java sucks. However, the books suck worse. Most of the books are long and filled with lame examples that only seem to dumb down the mind.

Did the way they encode tripcodes change?

>>44

looks longer to me.

>>43
U MENA FILLED WITH THE MASSIVE JAVA ENTERPRISE LIBRARY?

>>44
moot must've changed the salt... he's done it at least once in the past, too

https://en.wikipedia.org/wiki/Salt_(cryptography)

it will only affect secure tripcodes, i.e. #herp#derp or ##herpderp, not #herpderp

but remember, secure tripcodes are for jerks!

>>47
well shit

apparently shiitchan doesn't like parentheses at the end of links

try this:
https://en.wikipedia.org/wiki/Salt_%28cryptography%29

>>39
>of the type tuna
so the class tuna became a type?

thenewboston, huh?

>>29
And my first reaction was "Oh geeze, this person is pulling that one out of their ass".
Technically, that blurb can be considered "pulled out of my ass" since the explanation doesn't actually apply to any language in particular, its just a generalization (and my knowledge in compiler construction is a bit rusty)... I did anticipate the usual derision so I've added the "plus other stuff" clause as the implementation details of object oriented languages are pretty diverse and what is and what isn't considered basic properties of object oriented isn't gospel. Reading it over again it could be argued that I've forgotten inheritance references (though, that could just be a magic "name" in an implementation), so for single inherited classes in particular there could be a cell in the class record to hold a reference to a super class symbol to cascade allocation.

Java is a very specific implementation of a flavor of ``object oriented'' and its structure is baked to the hard drive as class files which is readily described in chapter 4 of the JVM spec, however; I feel that it shows "more than needed" because it combines the job of a traditional executable blob with a class blueprint, with all the disadvantages that brings it.

How do you feel I should improve my description of a class?

>>49
The class Tuna is just a blueprint for the object.

>>51
Uhh...no comment.

>>51
tl;dr

;_;