Age | Commit message (Collapse) | Author | |
---|---|---|---|
2014-11-19 | Further runtests.py improvements. | John MacFarlane | |
Better handling of br. Distinguish between a case where there's space on the next line and one where there isn't. Added --test-normalization flag to test normalization feature. | |||
2014-11-19 | Improved normalization in runtests.py. | John MacFarlane | |
Closes #161. | |||
2014-11-18 | Added python version of test runner. | John MacFarlane | |
This tests the dynamic library when run without a second argument. The code makes use of an amended version of the normalization method from karlcow/markdown-testsuite. Closes #161. | |||
2014-11-18 | make test: Use cmake to run tests. So we get api tests too. | John MacFarlane | |
2014-11-18 | Add api_test directory to archive. | John MacFarlane | |
2014-11-18 | Merge branch 'api_tests' of https://github.com/nwellnhof/CommonMark into ↵ | John MacFarlane | |
nwellnhof-api_tests | |||
2014-11-18 | Removed remarkable.js benchmark. | John MacFarlane | |
2014-11-18 | Fix api_test warnings | Nick Wellnhofer | |
2014-11-18 | Set compiler flags for api_test | Nick Wellnhofer | |
2014-11-18 | Add header file to CMake api_test sources | Nick Wellnhofer | |
2014-11-18 | Try to support older CMake versions | Nick Wellnhofer | |
2014-11-18 | Boldface commonmark.js too in benchmarks. | John MacFarlane | |
2014-11-18 | Added a few more benchmarks. | John MacFarlane | |
2014-11-18 | Start with tests for the C API | Nick Wellnhofer | |
The C API tests can be run individually via build/api_test/api_test Or together with the spec tests via cmake --build build --target test | |||
2014-11-18 | Add node constructor and accessors to the public API | Nick Wellnhofer | |
The approach I'm taking is to copy inline literals internally to NULL-terminated C strings if requested by an accessor. This allows to return a 'const char *' that doesn't have to be freed by the caller. | |||
2014-11-18 | Make render_html support nodes with no children | Nick Wellnhofer | |
For empty inline nodes like EMPH, the parser always creates a child containing an empty string. Using the tree manipulation API, nodes with no children can be created. Adjust render_html to cope. | |||
2014-11-18 | Added remarkable.js benchmark. | John MacFarlane | |
2014-11-18 | Initialize all fields in node when creating inlines. | John MacFarlane | |
2014-11-18 | Fix to #205 that doesn't require raw HTML. | John MacFarlane | |
2014-11-18 | Updated benchmarks. | John MacFarlane | |
2014-11-18 | html: Removed union from RenderStack. | John MacFarlane | |
It doesn't make sense to have a union here, and this simplifies the code. | |||
2014-11-18 | Merge pull request #206 from nwellnhof/improve_node_check | John MacFarlane | |
Improve output of tree integrity check | |||
2014-11-18 | Improve output of tree integrity check | Nick Wellnhofer | |
2014-11-17 | Make sure the emph inline added in process_emphasis has a parent. | John MacFarlane | |
2014-11-17 | Set CMARK_DEBUG_NODES for debug builds. | John MacFarlane | |
2014-11-17 | Make parse_inlines add directly to parent. | John MacFarlane | |
Previously parse_inlines returned a list of parsed inlines. This had to be added to the parent, and fix_parents had to be called to manually add the 'parent' links to the children, and the 'last_child' link to the parent. Now parse_inlines takes the parent block as a parameter, and uses cmark_node_append_child to add the children, so that the pointers should be properly managed. This avoids the need for the fix_parents pass. | |||
2014-11-17 | Set last_child and parent in make_link | Nick Wellnhofer | |
2014-11-17 | Store link labels as children in tree structure | Nick Wellnhofer | |
2014-11-17 | Set prev, parent and last_child for inlines | Nick Wellnhofer | |
2014-11-17 | Move cmark_free_nodes to node.c | Nick Wellnhofer | |
2014-11-17 | Rename ast.h to parser.h | Nick Wellnhofer | |
2014-11-17 | Move reference type definitions to reference.h | Nick Wellnhofer | |
2014-11-17 | Move inline-related stuff to inlines.c | Nick Wellnhofer | |
2014-11-17 | Move public stuff from node.h to cmark.h | Nick Wellnhofer | |
2014-11-17 | Remove old node_block and node_inl | Nick Wellnhofer | |
2014-11-17 | Switch cmark_node_inl over to cmark_node | Nick Wellnhofer | |
2014-11-17 | Switch cmark_node_block over to cmark_node | Nick Wellnhofer | |
2014-11-17 | Start with unified nodes | Nick Wellnhofer | |
2014-11-17 | Merge pull request #205 from jesstelford/patch-1 | John MacFarlane | |
Fix display of triple-backtick to be cross-renderer | |||
2014-11-18 | Fix display of triple-backtick to be cross-renderer | Jess Telford | |
GitHub Flavored Markdown (where this README.md is rendered) was showing the triple tick as <code> </code>\`<code> </code>. This fixes it to correctly display 3 backtick characters when rendered. Tested in reference implementation, Github, and dillinger.io | |||
2014-11-17 | Make benchmarks.md table properly aligned. | John MacFarlane | |
2014-11-17 | Put benchmarks in separate benchmarks.md file. | John MacFarlane | |
2014-11-17 | More 'make bench' improvements. | John MacFarlane | |
2014-11-17 | More 'make bench' improvements. | John MacFarlane | |
2014-11-17 | 'make bench': Use larger benchmark file, fewer runs. | John MacFarlane | |
2014-11-17 | More 'make bench' improvements. | John MacFarlane | |
2014-11-17 | Improved 'make bench'. | John MacFarlane | |
2014-11-17 | Better benchmark. | John MacFarlane | |
'make bench' runs the program 20 times against a file composed of 10 copies of Pro Git (about 5MB in all). It then does statistics on the results. We run it with high priority to get more consistent timings. | |||
2014-11-17 | Merge pull request #203 from gcrico/Issue-202 | John MacFarlane | |
Fix Issue 202 - Catch RangeError thrown by native String.fromCodePoint (js) | |||
2014-11-17 | Fix Issue 202 - Catch RangeError thrown by native String.fromCodePoint (js ↵ | Guillaume Crico | |
implementation) When using a JS engine that provides a native String.fromCodePoint ES6 implementation (e.g. SpiderMonkey), a RangeError is thrown if the codepoint is invalid. When adding the from-code-point.js polyfill, the js implementation was modified in order to handle invalid code point by returning the 0xFFFD placeholder glyph. So this is not a real "polyfill", but an specific implementation (adapted to the parser needs). So, if a native String.fromCodePoint implementation is availbale, the fromCodePoint function should catch the RangeError and return the 0xFFFD placeholder glyph. |