Error Buddy
Do you have an error message from your application? Then find the answer with Error Buddy. You can search over 40000 source code files and troubleshooting documents using our beta lucene/nutch search interface or if you prefer, search as normal using google. With LXR technology you can drill right down into the line of source code where it came from with full cross-referencing.
If after searching you didn't get your ideal answer, or you are still unclear what the error means, you can choose to post that question to the community forums following the link included in the search results.
[1.6]001 ******** 002 * * 003 * TODO * 004 * * 005 ******** 006 007 Lifetime of result Value Tree, make sure we keep pointers. Exslt 008 handling of node set values is especially nasty in this respect, 009 lots of potential mem leaks... 010 011 Pattern tester: 012 -> try to optimize for ID scan and tests. 013 014 Pattern scanner: 015 -> add error checks on all returns 016 017 Sorting: 018 -> add lang and case-order 019 -> add foreign sorting functions (interfaces ?). 020 021 ******** 022 * * 023 * DONE * 024 * * 025 ******** 026 027 Design: 028 - should transforms for a given stylesheet be thread clean, 029 -> the precompilation now occur only at stylesheet processing 030 time (except the binding for named templates and extension 031 functions which need to be computed once at run-time). 032 Multiple threads should be able to reuse the same stylesheet 033 now. 034 035 Embedding Stylesheets: 036 - example in 2.7 would force to validate, we do it by default now 037 038 ID and Key support: 039 -> Done 040 041 Extra functions: 042 -> document() should not be a problem since Result Tree Fragments are 043 implemented 044 => Done 045 046 Templates: 047 -> check the built-in template rule for attributes 048 -> make sure @xxx matches are applied 049 050 Contextual error reporting: 051 -> provide a couple of functions providing context analysis, not urgent 052 053 Validity: 054 -> should we add validation by default ? Make this an option 055 -> redirrect validity errors 056 => done added a special parsing mode 057 058 Import: 059 -> parse them 060 -> provide functions to circulate in the import tree of stylesheets 061 -> make sure we use the cascade wherever it's needed 062 063 Extra functions: 064 -> make a separate module. 065 => done functions.[ch] 066 067 Support Attribute value templates: 068 -> starts to be urgent. Design it in flexible ways but try to optimize 069 to handle most of it at the stylesheet parse time ... 070 => Done for the most part need to check all attributes in XSLT constructs 071 using them and use the dedicated readin function. 072 -> optimization by checking their existence at stylesheet parse time. 073 => done when building the preproc function 074 075 Sorting: 076 -> add support for imbricated sorts 077 => done but not well tested. 078 079 Separate util module: 080 -> macros, config, verbosity ? 081 => xsltutils.[ch] 082 083 Support for disable-output-escaping="yes": 084 -> looks problematic, libxml has no support for anything like this, 085 and unless adding a new node type :-( or tweaking text node and 086 output routines this is gonna be messy ... must be handled at libxml 087 level. 088 => Done with a trick, text node name is different, requires > 2.2.11 089 090 Pattern scanner: 091 -> compute priority 092 -> handle unions 093 -> support for mode 094 => done 095 096 Pattern tester: 097 -> also put fast lookup for "text()", "comment()", "node()" 098 based patterns lists. 099 => done 100 101 Support Attribute value templates: 102 -> namespace support for attribute value templates is not done, need 103 a small API redesign 104 105 Doc: 106 - put a page at http://xmlsoft.org/XSLT/ 107 - generate/transform the DocBook to HTML 108 - add HTML to package 109 - manpage and doc for xsltproc 110 111 112 Error handling: 113 -> check the version stuff, design a separate module for error interfacing 114 and default handling, parsing vs. runtime, fatal / compat / warning, 115 and lack of optionnal features. 116 -> reports context 117 118 ID and Key support: 119 -> done but namespace support in keys is not defined 120 -> make sure keys are recomputed on new document input 121 122 Profiler: 123 -> added looks good enough 124 -> autocorrection of initial calibration loop
Testing
