Well, I recall reading something about Plucene, the Perl port of Lucene, being very difficult to get performant. After optimization it was uniformly slow because of many method calls. This wasn't really a problem in Java but was a problem in Perl.

(this is what I recall, a quick Google session didn't find me the mail or post I remember reading about this. Plucene developers would obviously know the real story here.)

But it is interesting what we do with this issue. Named parameters is a very common idiom. It is a very good idiom, in that it leads to maintainable code.

So, what can we do to make it perform better? Some special optimization of this case in the perl implementation? Some new syntax to support this idiom? Could it be related to the new named arguments being proposed for perl 5.12?

/J

---

---

• 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 How to display code and escape characters are good places to start.