summaryrefslogtreecommitdiff
path: root/ext/xslt
Commit message (Collapse)AuthorAgeFilesLines
...
* No need to show these if they are not used.foobar2001-05-081-5/+6
|
* Check for the existance of the iconv librarySterling Hughes2001-05-011-0/+17
| | | | | | | # Not sure if this is correct, I can verify that it doesn't break anything # and it logically looks like it would work. Can someone test this (BSD # and/or Windows)
* Add the xslt_make_array and xslt_free_array api functions (C level).Sterling Hughes2001-04-274-132/+132
| | | | | | | | Change the naming to be a bit more standard for a few of the existing api functions. Make the sablotron backend compile with these changes.
* Add a readme, this is a substitute to the e-mail I was going to send. itSterling Hughes2001-04-261-0/+281
| | | | | | gives a basic overview of the new xslt extension and goes into the details of the api, etc.
* Add a free function to free the returned structure.Sterling Hughes2001-04-262-4/+25
|
* Add the parse_xslt_arguments api function which parses sablotron typeSterling Hughes2001-04-262-0/+89
| | | | | arguments into an easy to use structure.
* Add an experimental version of the new XSLT extension. This is by no meansSterling Hughes2001-04-268-0/+1979
to be used on anything production, if you want to test it, beware, it may or may not work (feel free to complain to me if it doesn't work, or shower praise if it does work)... Mainly in PHP's CVS so that work on the other backends can take place. The api (function_entry) is what I'm thinking of for all backends. Every backend simply needs to define these functions, I'll send an e-mail describing all this in a bit....