Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

Re: class design: When to use static methods?

Back to article view | Back to comp.lang.java.programmer

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#24607 — Re: class design: When to use static methods?

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

[toc] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web