No, he means the pseudo constructor, before and outside of any of the
methods within Application.cfc.
On Tue, Apr 29, 2008 at 1:56 PM, Andrew Scott
[EMAIL PROTECTED] wrote:
pseudo constructor?
I think, you mean defined as local variables to that component.
--
mxAjax / CFAjax docs and other
I wouldn't call that a pseudo constructor. I do realise thats what has
been adopted, does it make it right. No I don't believe so.
Because technically it is not I do know that is what people are
saying, and for the life of me I do not know why.
Consider this then..
cfcomponent
. Set
pseudo constructor is pretty much the de-facto way to describe code that
runs outside of any cffunction tags in a CFC. I'd actually argue that by
trying to come up with yet another way to label it, you're inadvertently
making it more confusing than it already is. Sometimes you just have to obey
I am aware of that, I just don't need to agree with it.
On Tue, Apr 29, 2008 at 10:34 PM, Brian Kotek [EMAIL PROTECTED] wrote:
pseudo constructor is pretty much the de-facto way to describe code that
runs outside of any cffunction tags in a CFC. I'd actually argue that by
trying to come up
I was under the impression that a pseudo constructor was a function that
returns itself...and that the code above the cffunction tags are the
properties of the object.
On Tue, Apr 29, 2008 at 8:34 AM, Brian Kotek [EMAIL PROTECTED] wrote:
pseudo constructor is pretty much the de-facto way to
I was under the impression that a pseudo constructor was a
function that returns itself...
That would be an actual constructor. CF doesn't support that, so all we can
do is set properties. Many people refer to these properties collectively as
a pseudo-constructor.
Dave Watts, CTO, Fig Leaf
I wouldn't call that a pseudo constructor. I do realise thats
what has been adopted, does it make it right. No I don't believe so.
Because technically it is not I do know that is what
people are saying, and for the life of me I do not know why.
Since pseudo constructor isn't a
Since I am feeling froggy..
http://wordnet.princeton.edu/perl/webwn?s=pseudo
not genuine but having the appearance of
If we called it a constructor it certainly would be wrong but pseudo
constructor is pretty freaking accurate. Crap (I know a very technical term)
that falls inside cfcomponent
Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Christopher Vigliotti [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 30 April 2008 1:46 AM
To: CF-Talk
Subject: Re: APPLICATION scope unknown in Application.cfc
I was under
Subject: RE: APPLICATION scope unknown in Application.cfc
I was under the impression that a pseudo constructor was a
function that returns itself...
That would be an actual constructor. CF doesn't support that, so all we can
do is set properties. Many people refer to these properties
Adobe's own coding guidelines if I read it right says this.
cfcomponent
... Local variables
... public variables
... Pseudo constructor (if required)
... Public methods
... Package methods
... Private methods
/cfcomponent
And although it is unclear, it does
Hi,
I have this in my Application.cfc:
cffunction name=onApplicationStart access=public hint=Initialize
application parameters
cfset basepath =
#Left(ExpandPath('.'),FindNoCase(wwwroot,#ExpandPath('.')#)-1)#
cfset APPLICATION.mappings={}
cfset
The error says that the component components.security can't be located. It
doesn't say anything about the application scope.
On Mon, Apr 28, 2008 at 5:26 PM, marc -- [EMAIL PROTECTED] wrote:
Hi,
I have this in my Application.cfc:
cffunction name=onApplicationStart access=public
Hi Brian,
You're right, I put the question wrong. Sorry about that.
The issue is this:
if I define 2 mappings like this
cfset THIS.mappings={}
cfset THIS.mappings[/components]=D:\www\components
cfset THIS.mappings[/includes]=D:\www\includes
outside onApplicationstart() but inside the
Yes, they have to be defined in the THIS scope of Application.cfc.
On Mon, Apr 28, 2008 at 6:05 PM, marc -- [EMAIL PROTECTED] wrote:
Hi Brian,
You're right, I put the question wrong. Sorry about that.
The issue is this:
if I define 2 mappings like this
cfset THIS.mappings={}
cfset
ColdFusion is annoyingly particular about this try putting a / at the end of
your mapping declaration.
cfset THIS.mappings={}
cfset THIS.mappings[/components/]=D:\www\components
cfset THIS.mappings[/includes/]=D:\www\includes
Adam Haskell
On Mon, Apr 28, 2008 at 6:05 PM, marc -- [EMAIL
Oh I forgot... this.mappings is only going to work in the psuedo
constructor.
Adam
On Mon, Apr 28, 2008 at 6:05 PM, marc -- [EMAIL PROTECTED] wrote:
Hi Brian,
You're right, I put the question wrong. Sorry about that.
The issue is this:
if I define 2 mappings like this
cfset
that makes more sense.
Andrew Scott
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Adam Haskell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 29 April 2008 8:43 AM
To: CF-Talk
Subject: Re: APPLICATION scope
18 matches
Mail list logo
