> For my use cases, it's acceptable to expect the user to enter a > canonical path and expect the program to open the file with a > canonical path. I expect that there are other common use cases where > that's not acceptable.
That seems fine enough to start out with, and worry about more later. It might be that what users really want is just to be able to give fnmatch-style patterns (w/o FNM_PATHNAME) so it's easy to match multiple different ways to find a file name. That doesn't help with symlinks in the final component, of course. For that, you might really want to canonicalize both the name-to-match and traced names. Thanks, Roland ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Strace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/strace-devel
