DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25646>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25646 [PATCH] line and column numbers on fo:elements ------- Additional Comments From [EMAIL PROTECTED] 2003-12-23 21:21 ------- Somewhat leery on this one--What are the use cases you're proposing for this? Attaching this type of debugging to a heavily-called function such as FOTreeBuilder.characters() could be a relatively high performance hit--so I want to make sure this passes a "cost-benefit" analysis. As you see it, what are the benefits and what are the costs? Is this just for testing use or you anticipate this while running in production as well? The latter case, of course, would require more scrutiny. Also, isn't it more common to store Locator information within the callee? I.e., have the FObj.toString() just return information about its inherent data to the callee, and let the latter append Locator info (or whatever else callee- specific) to it--in those areas where we need to do debugging, troubleshooting, etc. Thanks, Glen
