|
-
January 15th, 2010, 04:18 PM
#1
Ancient threads: why not to replay?
I see all the time people replaying to old threads and others who are saying it was wrong... so when is a thread considered as dead and why is it wrong to replay to a two or more years old thread?
win7 x86, VS 2008 & 2010, C++/CLI, C#, .NET 3.5 & 4.0, VB.NET, VBA... WPF is comming 
remeber to give feedback  you think my response deserves recognition? perhaps you may want to click the Rate this post link/button and add to my reputation 
private lessons are not an option so please don't ask for help in private, I won't replay
if you use Opera and you'd like to have the tab-button functionality for the texteditor take a look at my Opera Tab-UserScirpt; and if you know how to stop firefox from jumping to the next control when you hit tab let me know
-
January 17th, 2010, 11:24 AM
#2
Re: Ancient threads: why not to replay?
Would like to know also.
Although i haven't "bumped" any very old threads but still curious.
For example many people do not like to create new threads every day, instead they ask their help in old thread or they just have to something useful to add.
I don't like spamming forum with my questions.
Last edited by BytePtr; January 17th, 2010 at 11:26 AM.
Rate my post if i it was useful!
-
January 17th, 2010, 03:58 PM
#3
Re: Ancient threads: why not to replay?
While not technically wrong, why bother responding to a thread that is old? Chances are the OP already has discovered the answer.
If you need to find out the answer to the old question, then just post a new question. That way, folks answering can answer it in a current context without having to re-read all the old replies (which may no longer apply since the programming environments may be out of date).
Btw, by 'old' I'm referring to threads that are older than 6 to 12 months. That's my definition anyway and I'm sticking to it. :-)
Last edited by Arjay; January 17th, 2010 at 04:00 PM.
-
January 17th, 2010, 11:53 PM
#4
 Re: Ancient threads: why not to replay?
What if someone is searching for a succinct term in the subject line or body, and lands on the old thread?
It would be nice if that thread were resolved, so that an answer can be found by people other than the original poster.
I don't like unanswered threads that have a clear subject or content, that can be found with key words in a search.
A complete thread can be more helpful over time, as it can be re-read by visitors/members, without further comments.
If the subject line and content was poorly related to the answer to begin with, then I guess a new thread could be created with a more pertaining subject line, and hopefully an answer.
-
January 18th, 2010, 04:41 PM
#5
Re: Ancient threads: why not to replay?
A perfect example of why not to reply to an old thread.
http://www.codeguru.com/forum/showthread.php?t=219234
Last edited by Arjay; January 18th, 2010 at 04:57 PM.
-
January 18th, 2010, 04:55 PM
#6
Re: Ancient threads: why not to replay?
and here a counter-example why one should resurrect old threads
http://www.codeguru.com/forum/showthread.php?t=459972
@Arjay: I think you've pasted the wrong link, because both posts are dated today
win7 x86, VS 2008 & 2010, C++/CLI, C#, .NET 3.5 & 4.0, VB.NET, VBA... WPF is comming
remeber to give feedback you think my response deserves recognition? perhaps you may want to click the Rate this post link/button and add to my reputation
private lessons are not an option so please don't ask for help in private, I won't replay
if you use Opera and you'd like to have the tab-button functionality for the texteditor take a look at my Opera Tab-UserScirpt; and if you know how to stop firefox from jumping to the next control when you hit tab let me know
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote
