🚀 go-pugleaf

In article <BwyFuK.Hn5@mentor.cc.purdue.edu>, hrubin@pop.stat.purdue.edu (Herman Rubin) writes:
|> In article <1992Oct30.182002.11907@netcom.com> tjm@netcom.com (Thomas J. Merritt) writes:
|> >In article <BwxsF6.3DF@mentor.cc.purdue.edu> hrubin@pop.stat.purdue.edu (Herman Rubin) writes:
|> 
|> 			...................
|> 
|> >Herman,
|> >	Why don't you just post the real code rather than these uncompilable
|> >snipettes that don't convey what you are trying to do very well?  Are you
|> >afraid your ego will get deflated if someone shows you a better way to
|> >solve your problem?  From the code you have posted I am certain that there is
|> >a more structured way to accomplish your task with out any loss in performance.
|> 
|> I HAVE posted the real code.  Let me state the problem:  It is desired to

[rest deleted]

   No, not really, Herman. You posted a fragment, but with some globals and/or
macros referenced but never defined. With those undefined items, compilers
can't compile it, optimizers can't optimize it, and humans can only guess at
what it's supposed to do.

   Thank you for taking the trouble to post what you did. Since you went to
that much trouble, I am going to request that you go to a little more trouble.
Plese take the piece of code you did post. Wrap it into a function definition.
Write a little test routine to call the random number subroutine and verify
correct behavior (e.g. print out randoms, compute statistics, make a histogram,
whatever). Include enough header files so that it compiles. Make *sure* it
compiles, so we can all compile it. Make sure it operates correctly. Then post
The *whole* thing: random number generator and calling routine, and we can go
to town on it.

    A program fragment with undefined variables and/or macros is not a specif-
ication. A compilable piece of code is a specification of your problem. What's
more, it is a more concise, less ambiguous, and clearer specification than the
hundred and twenty lines of text I just deleted. Even better, we can test your
code against whatever we write for speed, size, and correctness. It'll be like
having dozens of high quality PhD's working on your problem for free. Go ahead:
post that code and make my day!
					- Lee Campbell  <elwin@media.mit.edu>