Nope, those numbers at the end are the memory address, so if it's the same object, the memory address would be the same. You can prove the same thing with some CF, just run the same code, but set OUTPUT="false" on your method. You'll see that the page buffer isn't copied into the function, and the results aren't copied out either. It still needs the buffer, of course, because you can capture generated content (CFSAVECONTENT) inside the function, or let it go to the stream with a CFABORT tag, it just will be killed off when the function exits.
cheers, barneyb On Fri, 25 Feb 2005 18:13:12 -0000, Adam Cameron <[EMAIL PROTECTED]> wrote: > > However, they still don't share a buffer, because as you point out, > they're all using different PageContext objects, even though they happen to > have the same content. > > Could it not be the same object, just different references to it? > > -- > Adam -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
