| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Zend compatibility patch | Zeev Suraski | 2001-07-30 | 1 | -3/+4 |
| | | |||||
| * | buffer was too small | Thies C. Arntzen | 2001-07-29 | 1 | -1/+1 |
| | | |||||
| * | - Get rid of ELS_*(), and use TSRMLS_*() instead. | Zeev Suraski | 2001-07-27 | 1 | -1/+1 |
| | | | | | | | | - Move to the new ts_allocate_id() API This patch is *bound* to break some files, as I must have had typos somewhere. If you use any uncommon extension, please try to build it... | ||||
| * | Fix folding and clean up some extensions | Rasmus Lerdorf | 2001-06-06 | 1 | -1/+2 |
| | | |||||
| * | defined HAVE_CONFIG_H to enable DSO extension support. | Rui Hirokawa | 2001-06-05 | 1 | -0/+4 |
| | | |||||
| * | vim-6 does folding - clean up a bunch of missing folding tags plus | Rasmus Lerdorf | 2001-06-05 | 1 | -0/+8 |
| | | | | | | some misguided RINIT and RSHUTDOWN calls in a few fringe extensions | ||||
| * | Make this compile. Killed one compile warning. | foobar | 2001-05-28 | 1 | -1/+1 |
| | | | | | | # I still get a lot warnings when compiling sablot.c | ||||
| * | compile goood, compile error baaad. | Sterling Hughes | 2001-05-28 | 1 | -2/+2 |
| | | |||||
| * | leftovers | Sterling Hughes | 2001-05-27 | 1 | -69/+19 |
| | | |||||
| * | Add the xslt_make_array and xslt_free_array api functions (C level). | Sterling Hughes | 2001-04-27 | 1 | -19/+79 |
| | | | | | | | | | 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 free function to free the returned structure. | Sterling Hughes | 2001-04-26 | 1 | -4/+24 |
| | | |||||
| * | Add the parse_xslt_arguments api function which parses sablotron type | Sterling Hughes | 2001-04-26 | 1 | -0/+74 |
| | | | | | | arguments into an easy to use structure. | ||||
| * | Add an experimental version of the new XSLT extension. This is by no means | Sterling Hughes | 2001-04-26 | 1 | -0/+139 |
| 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.... | |||||
