in reply to A very odd happening (at least. . . to me)
in thread Processing large files many times over

I (and probably others here) would be curious to see what is going on with your code, but when it's just thrown at the community in a big heap, it's not likely to be looked at. Reading raw code isn't much fun. I would suggest Doing these things will make the problem more accssible to the reader, and may even help you understand what's going on in your own code.

You might also want to outline what you have figured out about the problem so far. This is partly to help the reader, and partly to prove that you have invested your own time and interest. Sure, it's both annoying and a waste of your time to have to prove to a bunch of strangers in writing that you have "R'ed the FM" etc., but CS/IT people often seem to demand that proof before deigning to answer questions.

/s

  • Comment on Re: A very odd happening (at least. . . to me)

Replies are listed 'Best First'.
Re: Re: A very odd happening (at least. . . to me)
by chaoticset (Chaplain) on Jun 24, 2002 at 17:01 UTC
    I would also offer the point that your commenting style's a little difficult to follow. Consider throwing a little more whitespace at this code to make it more readable. (For instance: When a variable has a sufficiently advanced use as to require a long comment, consider putting a blank line above and below it, to visually separate it from the rest of the variables.)

    I realize that's not quite what needs to be done with the code, but believe me -- the easier your code is to read, the more likely you're going to get helpful responses.

    In case you're curious, there is a largish list of recommended practices for whitespace, comments, etc. Nothing there is set in stone, but nobody will complain if you do the things it outlines. ;)

    -----------------------
    You are what you think.