-
Notifications
You must be signed in to change notification settings - Fork 43
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix: redo TreeFindNode and TreeFindNodeWild
Given that some wildcard searches are broken, and there is ambiguity in the syntax for **** this change makes the following syntax changes: [[treename::]tagname{.|:}] Four single character punctuations '.' the child ':' the member '^' the parent '~' wildcard both member and child and these can be tripled to make breadth first searches '...' all children ':::' all members '~~~' all members and children '^^^' all parent four of these is a syntax error a special case would first translate *** to ~~~ (four of these is also a syntax error) however **** becomes ~~~* which is OK. Some examples a.b*.c - a child named c of a child starting with b of a member or child called a a.b*:c - a member named c of a child starting with b of a member or child called a a.b*~c -a member or child named c of a child starting with b of a member or child called a a.b...c - a child called c someplace under the child hierarchy under a.b a.b:::c - a member called c someplace under the member hierarchy under a.b a.b\~\~\~c - a child or member called c someplace under the child/member hierarchy under a.b a.b*\~\~\~ etc... Fixes issue #417 The new algorithm consists of: * use flex to scan (parse) the wildcard specification. Bison was not needed since the syntax is so simple. * find all the nodes on the initial call and place them in a list in memory. returning the 1st element * return elements from the list of found nodes until there are no more.
- Loading branch information
1 parent
ae545d9
commit 4de465e
Showing
15 changed files
with
3,416 additions
and
1,101 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.