| | 1 | As you can see comparing the PHP port to the original JS code, |
| | 2 | the spirit of what I want to do is implement the code in as |
| | 3 | similar a code algorithm as possible for now, until we're more |
| | 4 | sure the algorithm is either solid (bug free) or perhaps we |
| | 5 | decide on a better universal algorithm. |
| | 6 | |
| | 7 | But the more similar the code algorithm implementations are, |
| | 8 | the easier it will be to maintain the various ports if changes |
| | 9 | must occur. |
| | 10 | |
| | 11 | In as much as possible, my preference is to use core/built-in |
| | 12 | parts of each language rather than plugins. That lets the most |
| | 13 | people have a chance to use it. If that's not practical in some |
| | 14 | situation, fine, document it. But if possible, that's preferred. |
| | 15 | |
| | 16 | The test.minify.html file shows 4 different test inputs which |
| | 17 | exercise the algorithm and show the correct outputs. Those same |
| | 18 | tests should pass on the ports, obviously. |
| | 19 | |
| | 20 | Process would just be to fork this repo and add the files, in |
| | 21 | the style of "minify.json.rb" for ruby, for instance, and then |
| | 22 | send me a pull request. |
git.r.bdr.sh / rbdr / dotfiles / blame_incremental