Re: truncate-fail-diag failure on Solaris

Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> It's worth noting in documentation that with the replacement function, >> opening-for-write any name ending with a slash (regardless of >> whether the non-trailing-slashed name exists) will always fail. > > IMO that's already clear fr

Re: truncate-fail-diag failure on Solaris

Jim Meyering wrote: > It's worth noting in documentation that with the replacement function, > opening-for-write any name ending with a slash (regardless of > whether the non-trailing-slashed name exists) will always fail. IMO that's already clear from POSIX [1], which says: "A pathname that co

Re: truncate-fail-diag failure on Solaris

Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote in > : >> > You could see whether the file name ends in '/' before >> > you call open() on it, no? >> >> To work around such broken systems without polluting >> all ap

Re: truncate-fail-diag failure on Solaris

Jim Meyering wrote in : > > You could see whether the file name ends in '/' before > > you call open() on it, no? > > To work around such broken systems without polluting > all application code, in the past we've used wrapper >