Thanks for the reference Dave! :)
James Ang
Programmer
MedSeek, Inc.
[EMAIL PROTECTED]
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 9:55 AM
To: CF-Talk
Subject: RE: does StructNew() destroy old
> Memory deallocation, from my experience, happens at the
> end of a request. It makes sense that way, and that would
> be how I would implement the CFML interpreter engine anyway
> since all the engine needs to do is to keep track of the
> heap memory assigned to the thread performing the CFM
PROTECTED]
-Original Message-
From: Raymond Camden [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 9:16 AM
To: CF-Talk
Subject: RE: does StructNew() destroy old structure completely?
It doesn't harm anything at all. I guess you could say you don't need
struc
Subject: RE: does StructNew() destroy old structure completely?
It doesn't harm anything at all. I guess you could say you don't need
structClear(), but it's a matter of personal preference. If my intent
was to clear the struct, I'd use it just because it makes more sense t
Wednesday, September 18, 2002 12:07 PM
> To: CF-Talk
> Subject: RE: does StructNew() destroy old structure completely?
>
>
> so, like his question, does that muck
> things up at all? memory wise? just wondering.
>
> also, does it spell out the lack of need for structClear()
Message-
From: Raymond Camden [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 10:36 AM
To: CF-Talk
Subject: RE: does StructNew() destroy old structure completely?
structNew will kill the old data.
===
Raymond
structNew will kill the old data.
===
Raymond Camden, ColdFusion Jedi Master for Hire
Email: [EMAIL PROTECTED]
Yahoo IM : cfjedimaster
"My ally is the Force, and a powerful ally it is." - Yoda
> -Original Message-
7 matches
Mail list logo
