[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proposed pathchk change, in response to today's POSIX interpretation
From: |
Paul Eggert |
Subject: |
Re: proposed pathchk change, in response to today's POSIX interpretation |
Date: |
Fri, 07 Jan 2005 13:43:08 -0800 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
address@hidden writes:
> Is the full definition of what patchk deems
> portable available publicly?
The current standard is here:
http://www.opengroup.org/onlinepubs/009695399/utilities/pathchk.html
In addition to <http://www.opengroup.org/austin/interps/doc.tpl?gdid=6232>,
which I already mentioned, you probably also want to look here:
http://www.opengroup.org/austin/interps/doc.tpl?gdid=6233
> I attach my findnl util for reference.
Yes, that's the sort of thing that pathchk was designed for.
However, I see several quoting problems in findnl, e.g.
"...\{...".
Another example:
> #The following is clever if I say so myself
> expressions=`eval echo -n '$'expressions$level`
isn't portable, since you can't rely on either -n or backslash
handling with "echo". Better is something like this:
eval expressions=\$expressions$level