Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Hi Wally,

Having just done courses on Java and Enterprise Java recently (I just became an evil management/IT consultant) I rather like the traditional getSalary() and setSalary() and toString() accessor, mutator and accessor/casting (they teach us cool and inscrutable words too) method standard. They act as good visual cues as to what is going on in the program, whereas the overloading route is less obvious and may make maintaining the code harder.

In general though, I like the idea of standardised method names as it makes life so much easier: I'm doing a smidgeon of J++ coding at the moment and I was taught in (real) Java, which uses the standard ways of doing things, whereas the bastardised version we are currently using has subtly different implementations of the same libraries. This also includes some of the method names as far as I can tell (I could be wrong, the learning curve is still steep.)

I guess I'd say this as a final quip- it doesn't actually really matter, provided that they are carefully documented.


"What this book tells me is that goose-stepping morons, such as yourself, should read books instead of burning them."
       - Dr. Jones Snr, Indiana Jones and the Last Crusade

In reply to Re: Getter and Setter Function Names - content warning:contains references to Java by Elgon
in thread Getter and Setter Function Names by Wally Hartshorn

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (1)
As of 2021-12-04 11:20 GMT
Find Nodes?
    Voting Booth?
    R or B?

    Results (30 votes). Check out past polls.