Groups > comp.lang.java.programmer > #24607

Re: class design: When to use static methods?

From	Eric Sosman <esosman@comcast-dot-net.invalid>
Newsgroups	comp.lang.java.programmer
Subject	Re: class design: When to use static methods?
Date	2013-07-02 22:19 -0400
Organization	A noiseless patient Spider
Message-ID	<kr01dt$m8$1@dont-email.me> (permalink)
References	<methods-20130702164134@ram.dialup.fu-berlin.de>

Show all headers | View raw

On 7/2/2013 10:47 AM, Stefan Ram wrote:
>    Instance methods! They make the difference between
>    object-oriented programming in Java and procedural
>    programming in Java (according to the common believes).
>    And OOP is better than procedural programming, so we must
>    use instance methods! (according to the common believes)

     Not so long ago in a thread about "The invokeLater loop,"
you seemed quite pleased with a (perverted) use of the static
method SwingUtilities.invokeLater().  Does this transgression
against OOP principles bring a blush to your cheek?

     Or is the redness a result of blowing too much smoke?

-- 
Eric Sosman
esosman@comcast-dot-net.invalid

Back to comp.lang.java.programmer | Previous | Next | Find similar | Unroll thread

Thread

Re: class design: When to use static methods? Eric Sosman <esosman@comcast-dot-net.invalid> - 2013-07-02 22:19 -0400

csiph-web