Aha! I think that's the one that I'd seen before... Thanks! :)

Yeah, ultimately I'd rather have a getCallingTemplatePath() function
or maybe a #caller.cf_template_path# variable native in CF, but... in
failing that... Yeah, for efficiency's sake it's better to explicitly
declare the template path, but that's not so good for development
(writing code), and since we know this particular product (our asp)
has a really good ratio of dollars to performance, we can afford to
burn some performance on making this easier on our other programmers.
Though ultimately it won't be my call, it'll be my boss who makes the
decision.

> I've always handled this by throwing an exception,
> catching the error,
> and examining the stack trace.  Hardly elegant, but suits
> the need.
> Just wrap the functionality up in another custom tag that
> simply
> returns the full call stack, and then the code that calls
> the custom
> tag can figure out what piece it needs (the one directly
> 'above'
> getCurrentTemplatePath(), in this case).


s. isaac dealey     954.522.6080
new epoch : isn't it time for a change?

add features without fixtures with
the onTap open source framework

http://www.fusiontap.com
http://coldfusion.sys-con.com/author/4806Dealey.htm


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:217292
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to