Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uflorida!haven!mimsy!chris From: chris@mimsy.umd.edu (Chris Torek) Newsgroups: comp.lang.c Subject: Re: Is it time for comp.lang.c.dos? Message-ID: <23648@mimsy.umd.edu> Date: 10 Apr 90 21:04:25 GMT References: <1990Mar29.224413.21552@xenitec.on.ca> Distribution: usa Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 49 I wrote: >>There is, however, a `rule of thumb' that applies in cases like >>this: start with the smallest newsgroup that might apply. ... In article flee@shire.cs.psu.edu (Felix Lee) writes: >Well, for the example I gave, the smallest applicable newsgroup by >volume is ... [or] If you mean smallest category ... [or] smallest >distribution ... [or] If you mean smallest chance of a good answer .... I think I mean `by volume'. (Likelihood of applicability also applies, however.) >And if the problem really is a defect in my understanding of malloc(), >then comp.lang.c is the best newsgroup to ask. Indeed. To return to the original: >``I'm having a problem with malloc() in Utah.'' The problem has >nothing to do with Utah (I hope), but where is the defect? Is it my >understanding of malloc, my understanding of C, my Zortech C compiler, >my copy of GNU malloc, my Amiga computer, my homebrew operating >system, my extended memory board, or my neighbor's cat? In this case, a reasonable approach would be to pick the thing you think is the most likely source of error. For instance, if you think the problem is in the C implementation, post to a newsgroup dealing (as exclusively as possible) with that implementation. If you think the problem is most likely in the GNU malloc, post to gnu.. If you think the problem is most likely in your understanding of malloc, post to comp.lang.c. In any case, (a) state the problem; (b) give the details that are relevant to the newsgroup/problem-solving-group; (c) try to phrase the question such that it is relevant to the group. In other words, the comp.lang.c posting might say: ``I am not sure I am using malloc correctly. Here is the idea; here is the code. Is this correct? Please answer via electronic mail.'' while the comp.sys.amiga.tech posting might say: ``I tried the code below. It fails; I think it might be because there is a glitch in the extended memory hardware. If this is the case, how can I fix it?'' and so on. (Of course, you could post one article, cross-posted, with sections relevant to each newsgroup.) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@cs.umd.edu Path: uunet!mimsy!chris