From 1be560f69cd5db53b0278580ac589991f059802b Mon Sep 17 00:00:00 2001 From: c9s Date: Mon, 19 May 2014 10:40:39 +0800 Subject: [PATCH] fix changelogs --- CHANGES.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index f746604..b9287eb 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -4,21 +4,21 @@ API changes: 1. Removed the `route` argument from `r3_tree_insert_pathl`: - node * r3_tree_insert_pathl(node *tree, char *path, int path_len, void * data); + node * r3_tree_insert_pathl(node *tree, char *path, int path_len, void * data); -This reduce the interface complexity, e.g., + This reduce the interface complexity, e.g., - r3_tree_insert_path(n, "/user2/{id:\\d+}", &var2); + r3_tree_insert_path(n, "/user2/{id:\\d+}", &var2); 2. The original `r3_tree_insert_pathl` has been moved to `_r3_tree_insert_pathl` as a private API. 3. Moved `r3_tree_matchl` to `r3_tree_matchl` since it require the length of the path string. - m = r3_tree_matchl( n , "/foo", strlen("/foo"), entry); + m = r3_tree_matchl( n , "/foo", strlen("/foo"), entry); 4. Added `r3_tree_match` for users to match a path without the length of the path string. - m = r3_tree_match( n , "/foo", entry); + m = r3_tree_match( n , "/foo", entry); 5. Added `r3_tree_match_entry` for users want to match a `match_entry`, which is just a macro to simplify the use: