Hi
Andrew,
not
sure what else I can say about it except try and explain it in another
way.
When
referencing variables on a page it could error for any reason, i.e. not defined,
not a simple type etc. etc. I was thinking about having a bit more control on
what happens when it errors. For example:
<cfset myIncorrectVar = "Dear Sir,">
<cfmail ...>
#variables.IncorrectVar#
Rest
of the important message
In
this case variables.IncorrectVar is undefined, I don't feel its important enough
to abort the process, so something like
#obj.fnOutput( variables, 'firstName', 'nothing'
)# or #obj.fnOutput( variables, 'firstName', 'display' )#
would suit me better... And I have not thought
this whole process out yet, so it will probably still turn out to be a bad idea,
but I am looking to hear about those bad
ideas.
And by the way, on a or
I would use one of those error codes to notify the
system/developer. etc.... ;-))
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
Register now for the 3rd National Conference on Tourism Futures, being held in Townsville, North Queensland 4-7 August - www.tq.com.au/tfconf |
