Re: FindFirstFile Possible Memory Leak
- From: "Robert Morley" <rmorley@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Jun 2007 01:10:18 -0400
Of course, if he'd Dim'd his variables up top, like most people do, there
wouldn't be a single colon in the code. Makes me wonder if the code would
run any slower by Dim'ing in a loop, or if there's any memory advantage. I
know we had a related discussion a while back, but I don't remember if we
covered these issues or not.
Like you, I find multi-statement lines distracting, but I can live with it.
By posting that, though, you've virtually guaranteed that people will get
distracted as we debate the relative merits of multi-statement lines and now
I'm adding to it with the Dim issue. :-)
Rob
"Bob O`Bob" <filterbob@xxxxxxxxxxxxxxx> wrote in message
news:%23QpenVWrHHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
By the way, to limit how distracted people get here in the groups
by things irrelevant to your question, I *strongly* recommend you
rewrite the %$#^%$#^%ing colons out of your code before posting.
.
- Follow-Ups:
- Re: FindFirstFile Possible Memory Leak
- From: Michael C
- Re: FindFirstFile Possible Memory Leak
- References:
- FindFirstFile Possible Memory Leak
- From: Stefan Berglund
- Re: FindFirstFile Possible Memory Leak
- From: Bob O`Bob
- FindFirstFile Possible Memory Leak
- Prev by Date: Re: Compile Only
- Next by Date: Re: Compile Only
- Previous by thread: Re: FindFirstFile Possible Memory Leak
- Next by thread: Re: FindFirstFile Possible Memory Leak
- Index(es):