The problem with free'ing the %is_selected is just one symptom of a poor solution that doesn't scale.

The problem with freeing that is a problem with adding traits to a language which doesn't natively support them. It has nothing to do with whether or not the concept is appropriate.

As for the rest of what you typed, it might be a great way of looking at the problem but it's completely irrelevant to my specific coding problem. With runtime traits, my code is cleaner and easier to read. Solutions should be created to match actual problems faced, not "what if" scenarios -- unless those scenarios have a realistic chance of occurring. For the purposes of the code I was working on, it's been used for years and is quite stable. Your scenario is highly unlikely to apply.

---

---

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.