Journal FortKnox's Journal: Stupid Journal Entry 17
Stupid random writings of a tired, bored, yet terribly busy coder.
Some mock about Em crying from previous journal entry.
Some mock about Em crying from previous journal entry.
Insert (Score:1)
Re: (Score:2)
Re:Insert (Score:2)
Re: (Score:2)
Re:Insert (Score:2)
Re: (Score:2)
Didn't Sandler Do Something Like This? (Score:2)
Concentration...
Asexualization!
-cm
(I wish this code would do
Re: (Score:2)
Reply (Score:2)
Insult my own ignorance.
Re:Reply (Score:1)
Ok, then... (Score:2)
Re:Ok, then... (Score:2)
Getters and Setters are the door way between the private and the public. So they aren't necessary. However, this all brings up coding standards.
It's more readable to me because I don't have some code that uses getFoo() and some that uses m_blah.foo.
Thats poor programming and should be stamped out at inspection.
It gives you an opportunity to encapsulate logic related to getting and setting, such as a single place to do null checking or array bounds.
This is the strongest argum
Re:Ok, then... (Score:2)
2.) I always use the MVC pattern (Model View Controller). If you use it correctly, the view should only contain JSP based info on displaying the pages. Therefore, in your view package, you'd have a "jsp" package for displaying JSPs, and a package for (
Re:Ok, then... (Score:2)
imagine this as the last post (Score:1)
And now for something completely different... (Score:2)
jason