Significant Update - For Code Section

Noble Monks,

I think that there needs to be a "Significant Update" option for the Code Catacombs Section. This would be like the "Significant Update" on the user update section. It would let updated code make it back into Newest Nodes.

It has been my experience that posts are seldom stumbled upon unless they're in Newest Nodes (of course, they're easy to find if your looking for them, but that's not stumbling). If some code popped back up in Newest Nodes after the author had done some major updating (ex: a new version, more features) then readers could see it again in a new light.

One thing that's been done in the past is to create a seperate thread for each seperate version of a work. I feal that this is just spreading the code out a little more than is necessary.

Getting code back into Newest Nodes might also act as a motivational factor for monks who enjoy XP gains (like me :-) ) to maintain their works.

-Ben Jacobs (dooberwah)
http://dooberwah.perlmonk.org
"one thing i can tell you is you got to be free"

Comment on Significant Update - For Code Section

Replies are listed 'Best First'.

Re: Significant Update - For Code Section
by rjray (Chaplain) on Apr 04, 2002 at 22:59 UTC

Even setting aside the hunger for XP gains :-), I would think that something like this would be a good idea. I know that if I modify the code in-place, rather than re-posting it, there's probably a reason for this. Namely, I think that the old code should be superceded (whether this "new" code is distinctly different or just a mild bug-fix). I don't want the casual user to find both versions as a result of a search. And the minimalist in me doesn't want there to be 2+ nodes when only one is needed.

--rjray

[reply]


There's more than one way to do things
	PerlMonks