Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx05.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: class design: When to use static methods? Date: Tue, 02 Jul 2013 22:19:49 -0400 Organization: A noiseless patient Spider Lines: 17 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 3 Jul 2013 02:14:21 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="0d73d8cc209bff1c6395088b400d0605"; logging-data="712"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Lew5PkD7pJuLVB0lkBXHv" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 In-Reply-To: Cancel-Lock: sha1:VZ6PXPjF89daE3ZvQTUXPpUQxwc= Xref: csiph.com comp.lang.java.programmer:24607 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