testing. That's the problem with a lot of these which is
faster tricks -
they promise marginal performance gains, but people tend to
focus on them
all out of proportion to their importance in building a scalable,
high-performance application. I'd wager in a minute that, if
you can save
]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 5 June 2002 1:24 AM
To: CF-Talk
Subject: RE: unscoped variables
all unscoped variables are part of the variables scoped.
cfset temp = testing
cfoutput#temp#/cfoutput
is also
cfoutput#variables.temp
-
From: Peter Tilbrook [mailto:[EMAIL PROTECTED]]
Sent: 05 June 2002 09:20
To: CF-Talk
Subject: RE: unscoped variables
Does CFMX still use the application.cfm file? Or can you adopt an
alternative like Fusebox instead?
Silly question?
==
Peter Tilbrook
Macromedia ColdFusion Applications Developer
415
Email: [EMAIL PROTECTED]
-Original Message-
From: Neil Clark - =TMM= [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 5 June 2002 6:23 PM
To: CF-Talk
Subject: RE: unscoped variables
Silly question :-)
Yes it does. The Fusebox method doesnt really adopt anything per say
its just
: unscoped variables
Yeah. I just found that NOT using an application.cfm file on a
multi-site
server was problematic. Fusebox is still a great dev standard though,
==
Peter Tilbrook
Macromedia ColdFusion Applications Developer
4/73 Tharwa Road
Queanbeyan, NSW, 2620
AUSTRALIA
Phone: (02) 6284 2727
: unscoped variables
Yeah. I just found that NOT using an application.cfm file on a
multi-site
server was problematic. Fusebox is still a great dev standard though,
==
Peter Tilbrook
Macromedia ColdFusion Applications Developer
4/73 Tharwa Road
Queanbeyan, NSW, 2620
AUSTRALIA
Phone: (02) 6284 2727
Mobile
An interesting thing that many developers overlook, or
just don't know - is that there is actually a performance
increase in SETTING your variables scope variables as
well as reading them.
We all know that #variables.myVar# is faster than #myVar# -
It is slight, but yes - using cfset
I'm trying to clean up some code on an old application. If there are
currently unscoped variables defined using cfset on an application.cfm page,
what scope are these created in?
Thanks!
__
Signup for the Fusion Authority
If they are created in the Application.cfm page, they are application
variables (application.whatever)
Paul Giesenhagen
QuillDesign
- Original Message -
From: [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Tuesday, June 04, 2002 10:04 AM
Subject: unscoped variables
I'm trying
AFAIK variable scope unless scoped otherwise.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 04 June 2002 16:04
To: CF-Talk
Subject: unscoped variables
I'm trying to clean up some code on an old application. If there are
currently unscoped
all unscoped variables are part of the variables scoped.
cfset temp = testing
cfoutput#temp#/cfoutput
is also
cfoutput#variables.temp#/cfoutput
this happens no matter what page it is set on, includeing the
application.cfm. if you want a variables to be in the appliction scope, you
have
: unscoped variables
all unscoped variables are part of the variables scoped.
cfset temp = testing
cfoutput#temp#/cfoutput
is also
cfoutput#variables.temp#/cfoutput
this happens no matter what page it is set on, includeing the
application.cfm. if you want a variables to be in the appliction
/trial/
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: 04 June 2002 16:12
To: CF-Talk
Subject: Re: unscoped variables
If they are created in the Application.cfm page, they are application
variables (application.whatever)
Paul Giesenhagen
QuillDesign
]
cc:
06/04/2002 Subject: RE: unscoped variables
Sorta relates to this thread...one of the neatest things to do in MX is:
cfdump var=#variables#
Awesome for debugging.
jon
__
Structure your ColdFusion code with Fusebox. Get the official book at
I thought the variables scope was local to an individual
page. These variables (set unscoped in application.cfm)
are used throughout the entire application. That's why I
asked.
Whenever you set a variable in the local or Request scopes within
Application.cfm, that variable will be
No, they are not application scope by default if set in the
Application.cfm page. Unscoped variables set in the Application.cfm are
like unscoped variables set on a regular page.
On Tue, 4 Jun 2002, Paul Giesenhagen wrote:
If they are created in the Application.cfm page, they are application
.
Neil Clark
Team Macromedia
http://www.macromedia.com/go/team
Announcing Macromedia MX!!
http://www.macromedia.com/software/trial/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 04 June 2002 16:37
To: CF-Talk
Subject: RE: unscoped variables
I
variables.myVar = foo is faster than
cfset myVar = foo
=)
Nate Nielsen
[EMAIL PROTECTED]
- Original Message -
From: [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Tuesday, June 04, 2002 10:36 AM
Subject: RE: unscoped variables
I thought the variables scope was local to an individual page
16:45
To: CF-Talk
Subject: Re: unscoped variables
Sorta relates to this thread...one of the neatest things to do in MX is:
cfdump var=#variables#
Awesome for debugging.
jon
__
Your ad could be here. Monies from ads go to support
An interesting thing that many developers overlook, or just don't know -
is
that there is actually a performance increase in SETTING your variables
scope variables as well as reading them.
Very true, however, I find that the performance increase is not worth a
little bit messier code. I
And for those of us who still use 4.5, cf_dump is also a wonderful tool
for debugging!
Eric
-Original Message-
From: Neil Clark - =TMM= [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 04, 2002 12:10 PM
To: CF-Talk
Subject: RE: unscoped variables
cfdump was also in CF5 :-)
but yes
: unscoped variables
An interesting thing that many developers overlook, or just don't know - is
that there is actually a performance increase in SETTING your variables
scope variables as well as reading them.
We all know that #variables.myVar# is faster than #myVar# -
It is slight, but yes - using
I would just LOVE to see by how much.
001
Agreed. CF would check the scopes in order, starting with the query scope
(if in a cfoutput or cfloop) and then move onto the variables scope. I
could see how performance would increase if you were looking at scoping
SERVER
16:45
To: CF-Talk
Subject: Re: unscoped variables
Sorta relates to this thread...one of the neatest things to do in MX is:
cfdump var=#variables#
Awesome for debugging.
jon
__
Get the mailserver that powers this list
At 6/4/2002 10:12 AM -0500, Paul Giesenhagen wrote:
If they are created in the Application.cfm page, they are application
variables (application.whatever)
That's incorrect. Unscoped variables are created in the variables. scope no matter
where they are defined.
-Max
26 matches
Mail list logo
