Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | James Kuyper <jameskuyper@verizon.net> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Variable argument function as a parameter of a variable argument function |
| Date | 2011-11-21 07:22 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <jadfr4$n9u$1@dont-email.me> (permalink) |
| References | (2 earlier) <e6730a8e-3cb9-49a5-aaaa-c7a36945474d@o1g2000vbe.googlegroups.com> <lnaa7qwdm2.fsf@nuthaus.mib.org> <ab6d0b3a-83b3-4b48-a65b-b00fa41a97cb@g21g2000yqc.googlegroups.com> <jacafp$2a4$1@dont-email.me> <6e6c6503-88f2-41eb-a5e2-d584ee8d477b@q16g2000yqn.googlegroups.com> |
On 11/20/2011 11:18 PM, AikidoGuy wrote: >>> I asked my simpler issue first. >> >> The fundamental problem with taking that approach is that you're >> assuming that you'll be able to solve X, if Y turns out not to be the >> right solution. > > This is becoming very philosophical. It's not philosophy; it's hard practical advice about effective techniques for asking questions. >> If you know enough about X to justify that assumption, you should first >> try solving X on the assumption that Y is not the right solution; only >> ask about Y if not-Y leads you to a dead-end. > > My question to the group was about Y. I obtained answers about Y. > To question whether or not I am able to solve X is to question my > ability and not to answer my question. You shouldn't be thin-skinned about that. If you need to ask any question at all, that implies that there's some things you don't know about the topic of your question. There's nothing unusual about that, we all have gaps in our knowledge, just gaps of different sizes and in different locations. The more elementary the question, the more it implies that you don't know. This particular question implied a fairly basic misunderstanding about how functions worked, justifying a suspicion that there's a fair bit you don't know about C. It's quite common for people to ask the wrong question; questioning them to determine what the right question should have been is more helpful than answering the wrong question that they asked. The particular question you asked was so bizarre as to strongly justify a suspicion that this might be one of those cases. In particular, there's one key disadvantage to your approach that I didn't address in my earlier comments. What if Y did "solve" your problem, but was far from being the best solution? I've frequently seen questions about extremely complicated and elaborate "solutions", that could, when the questions had been answered, do what they were intended to do, but were extremely unlikely to be the best solution to whatever the real problem was. I've found that the people who ask these questions are almost never willing to describe the real problem that they're trying to solve, which makes it difficult to prove that they asked the wrong question. I suspect that they're embarrassed about something that they would have to explain - perhaps it's something illegal, or maybe just that they don't want people to see how bad their coding skills are. A few have claimed that they had security issues to worry about, which sounds fairly legitimate - but almost any code that poses security issues can be rewritten to present the same coding problem without violating security. >> If you do not know enough about X to justify that assumption, as is by >> far the most common case, asking about Y could end up drawing you into a >> long, drawn-out discussion of Y that does nothing to solve your real >> problem. In my experience on this newsgroup, such useless discussions >> are by far the most common result of the "XY" approach. > > Generalities are certainly nice things to state. And I am not up to > date on how others discuss their problems. So I apologize for my > inappropriate behaviour on this newsgroup. It's not inappropriate behavior; it's an unproductive approach to asking for help. -- James Kuyper
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Variable argument function as a parameter of a variable argument function AikidoGuy <aikidoguy@gmail.com> - 2011-11-19 23:02 -0800
Re: Variable argument function as a parameter of a variable argument function Ark <akhasin@macroexpressions.com> - 2011-11-20 03:14 -0500
Re: Variable argument function as a parameter of a variable argument function Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-11-20 08:07 -0500
Re: Variable argument function as a parameter of a variable argument function Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-11-20 08:11 -0500
Re: Variable argument function as a parameter of a variable argument function Keith Thompson <kst-u@mib.org> - 2011-11-20 08:19 -0800
Re: Variable argument function as a parameter of a variable argument function pete <pfiland@mindspring.com> - 2011-11-20 13:33 -0500
Re: Variable argument function as a parameter of a variable argument function AikidoGuy <aikidoguy@gmail.com> - 2011-11-20 15:29 -0800
Re: Variable argument function as a parameter of a variable argument function Keith Thompson <kst-u@mib.org> - 2011-11-20 15:58 -0800
Re: Variable argument function as a parameter of a variable argument function AikidoGuy <aikidoguy@gmail.com> - 2011-11-20 16:05 -0800
Re: Variable argument function as a parameter of a variable argument function James Kuyper <jameskuyper@verizon.net> - 2011-11-20 20:45 -0500
Re: Variable argument function as a parameter of a variable argument function AikidoGuy <aikidoguy@gmail.com> - 2011-11-20 20:18 -0800
Re: Variable argument function as a parameter of a variable argument function James Kuyper <jameskuyper@verizon.net> - 2011-11-21 07:22 -0500
Re: Variable argument function as a parameter of a variable argument function Seebs <usenet-nospam@seebs.net> - 2011-11-21 22:43 +0000
csiph-web