On Sat, Mar 25, 2017 at 2:30 PM, Dennis Kaarsemaker <den...@kaarsemaker.net> wrote: > >> - does this code do a reasonable thing when the path is a symbolic >> link that points at a directory? what does it mean to grab >> st.st_size for such a thing (and then go on to open() and xmmap() >> it)? > > No, it does something entirely unreasonable. I hadn't even thought of > testing with symlinks to directories, as my ulterior motive was the > next commit that makes it work with pipes. This will be fixed.
To be quite honest, I do not mind it if the "toplevel pipe that came from the command line is treated as if it were a regular file" was the only change in this series, without doing anything for symbolic links. I do not use the process substitution myself, but I can see why sometimes it is handy to pass two process invocations on the command line of "diff" (if it were only one, then "-" with the usual redirection already works, but you cannot do two command using that syntax). Perhaps we can have only that part and perfect it first and have it ready for the next release, postponing the symlink dereferencing, which is a different issue?
