For files of moderate size – or if you really don't care how long it takes – the sort-compare subroutine can also be programmed to split the key string into its component parts every time. The components are then compared by the subroutine as has already been shown. The difference is the classic trade-off between "speed versus space." Splitting all the strings ahead of time saves time but costs memory and vice-versa. (Because of the number of times a sort-compare subroutine might be executed, the difference in speed can be substantial.) Also note that many external sort-commands are quite capable of handling delimited-string keys efficiently, such that you might not actually have to "write a program" to get the job done.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.