Main Task
The best thing about the GNU find is it's expression evaluation and multiples compound checking which can be passed like as arguments
Current Situation
ffind currently searches and finds the directory faster than GNU find but still doesn't have that complex expression evaluation.
Objective
So the next task is to code transplant the amazing work which is there in the GNU find for expression building and evaluation
Search and Found
GNU findutils main repo : findutils
There expression evaluation starts here
// find/ftsfind.c Line : 770
int
main (int argc, char **argv)
{
...
eval_tree = build_expression_tree (argc, argv, end_of_leading_options);
...
}
Which follows to this file
// find/tree Line : 1246
struct predicate*
build_expression_tree (int argc, char *argv[], int end_of_leading_options)
{
...
}
Final Follow up
The final objective is to build a function that does something like
int
is_valid_path(char[] path, struct predicate* eval_tree)
{
// compare the path with the eval_tree to find if the path satisfies it
}
Main Task
The best thing about the GNU find is it's expression evaluation and multiples compound checking which can be passed like as arguments
Current Situation
ffindcurrently searches and finds the directory faster than GNU find but still doesn't have that complex expression evaluation.Objective
So the next task is to code transplant the amazing work which is there in the GNU find for expression building and evaluation
Search and Found
GNU findutils main repo : findutils
There expression evaluation starts here
Which follows to this file
Final Follow up
The final objective is to build a function that does something like