When is the S.T. the way to go for sorting? And why? Does it win you efficiency, or is it mainly just for readability? Can some wise ones present the community with scenarios when you just should to use S.T., versus sorting some other way?

(decided to do a SOPW on this after posting Re^2: Sorting an array on two computed fields.)

I feel like this has probably already been discussed elsewhere, but my preliminary searches didn't pull any slam dunks, so please link to where the good stuff is if you know!

UPDATE: After reading some of the follow up links posted, I understand why "Schwartzian" sort performs better when the sort involves calling an expensive filesystem call, such as chcking file size. (See in particular Benchmark, -s versus schwartzian)

I now wonder... are there other general types of situation where it "pays"?

UPDATE 2: However, merlyn concedes that the -s (file size operator) for showing off S.T. may actually be a bit contrived: Re: Benchmark, -s versus schwartzian.

UPDATE 3: Merlyn also characterizes S.T. as a less "ideal", but much more maintainable, approximation of sort using another technique, the GRT (Guttman Rossler Transform): •Re^4: Benchmark, -s versus schwartzian

---

---

• 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.