Re: Passing a Method Name to a Method

From:

Eric Sosman <esosman@ieee-dot-org.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 24 Jun 2011 07:48:06 -0400

Message-ID:

<iu1tj7$vf4$1@dont-email.me>

On 6/23/2011 5:44 PM, Gene Wirchenko wrote:

On Wed, 22 Jun 2011 22:30:42 -0400, Joshua Cranmer
<Pidgeot18@verizon.invalid> wrote:

[snip]

       static returntype ThisWay(formal parms)
          {...}

       static returntype ThatWay(formal parms)
          {...}

Why are you having static methods (on the same class, I presume) for two
different ways of parsing instead of using separate parser classes?

I am not writing different parsers. I am writing different
methods for handling a small (but frequently called) part of the
parsing. I wish to test how fast each of these methods are.

As an aside: You're certainly aware that micro-benchmarks are
easy to concoct, but notoriously difficult to interpret. In Java,
concoction is equally easy but interpretation is *much* harder.
"Do X N times, do Y N times, measure the elapsed times" simply doesn't
work well in the face of just-in-time compilation, garbage collection,
the loading of ancillary classes, and so on.

--
Eric Sosman
esosman@ieee-dot-org.invalid