I was just pointing out that people might not be interested in your findings, mostly if they are nothing special but just how - rhino mocks in this case - it is expected to work. I didn't force anyone to stop writing or anything else, so there's no need to put up a flame.
On Fri, Oct 10, 2008 at 3:36 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > I haven't got Paul's message yet (gmail is acting funny), so I am replying > here. > > There is no style for this list :-) > > The reason that I posted the challenge was explicitly to involve more > people in the project. And I did this with the full expectation that they > would have to go into a pretty big and pretty complex code base. > It is natural to get lost on first sight of such a code base, and questions > about it should be encouraged and answered. > > From the several messages to which I did answer, it seems like Paul's had > exactly the same reaction to an unfamiliar code base as most of us would > have. > Even for silly questions, which I don't think those were, an appropriate > response would be to put to the documentation or some reference. > > If, and only if, we are inundated with people asking silly questions we can > start pointedly referring them to the documentation. And I, for one, would > be happy to have that problem. > > > On Fri, Oct 10, 2008 at 3:25 PM, Stuart Laughlin <[EMAIL PROTECTED]>wrote: > >> >> On Fri, Oct 10, 2008 at 7:16 AM, webpaul <[EMAIL PROTECTED]> wrote: >> > >> > Simon is certainly right in that I've bit off a bigger piece than I >> > thought I was. I've only used Rhino Mocks in a few limited ways and >> > didn't realize there was more to it, so clearly I need to take some >> > more time to understand things. Seems like the style here is to go >> > away, finish a problem and come back instead of talking about it while >> > working on it. So I'll spend some more time understanding things and >> > see what I can do then. >> > >> >> Can I chime in as a rhino-tools-dev lurker? >> >> Coming back with a complete final solution is good, but seeing how it >> was worked out is better. Most people, when posting a final solution, >> don't have time to write up a concise explanation showing how their >> code evolved, their false starts, etc. This is totally understandable >> and why I argue that it's good to talk about the solution while >> working on it. >> >> Regardless of whether you agree with that or not, I would like to >> think that we can all agree that calling someone who does this a >> spammer is completely out of line. Not only is it a patently false and >> inflammatory accusation, but the message that conveys the accusation >> is ironically much more spam-like than what's being complained about >> in the first place, since it's completely off-topic and worth less >> than nothing in the list archives (similar to my own message, I might >> add). >> >> For people who don't want to see a lot of list messages go by, there >> are email clients with a threaded display (like GMail), and there are >> digest and summary options available on the list. You may read this >> list any way you choose, or not at all. >> >> This is certainly not intended as a personal attack on Simone, but >> rather an attack on this particular behavior of complaining about >> people who use the list in a way someone deems inappropriate for one >> reason or another (which has, of course, occurred on every list since >> time immemorial). >> >> >> --Stuart >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
