Yes Robin I got your post
 
Unfortunately I didn't read yesterdays posts about the original "issue", but in my opinion if you are going to call a function something vague like "tr", you might want to know where it comes from so you don't spend ages trying to figure it out later on when you forget what "tr" means.
 
Hence it makes sense to have at least a line in there somewhere to define what "tr" is - whether it's a comment saying where it is defined or simply an include that makes it obvious where the function is; i.e.
 
application.tr
..that means my function might be defined in the application
 
<cfinclude template="globalfunctions.cfm">
..that means my custom function might be in there
 
<!--- tr is in the application.cfc --->
..etc
 
I apologise if I am just making noise. Robin I didn't read your post at first.. Perhaps others didn't either. It like a stone of goodness in a river of..
 
Joel
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]On Behalf Of Robin Hilliard
Sent: Thursday, 29 June 2006 3:11 PM
To: [email protected]
Subject: [cfaussie] Re: Includes

No, that's exactly what the code I pasted into this thread 2 hours ago does...

Could someone tell me that they saw that post - I'm beginning to suspect I have a problem posting to cfaussie.

Robin

On 29/06/2006, at 3:04 PM, Dale Fraser wrote:

Ok,

To close this off and not waste eveyone’s time.

Is it safe to say, that it can’t be easily done. Ie you can’t automatically have a unscoped function name available to every page.

Regards
Dale Fraser



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cfaussie" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~----------~----~----~----~------~----~------~--~---

Reply via email to