This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Little cygpath improvement request
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 16 Feb 2014 02:08:34 -0500
- Subject: Re: Little cygpath improvement request
- Authentication-results: sourceware.org; auth=none
- References: <111910987 dot 20140214222230 at mtu-net dot ru> <52FE6397 dot 5010105 at cygwin dot com> <187072112 dot 20140214234339 at mtu-net dot ru> <20140215125606 dot GM2246 at calimero dot vinschen dot de> <1745533059 dot 20140215225708 at mtu-net dot ru> <2826041 dot 20140216062749 at yandex dot ru> <53004F35 dot 4020301 at googlemail dot com> <1793681198 dot 20140216102125 at yandex dot ru>
- Reply-to: cygwin at cygwin dot com
On 2/16/2014 1:21 AM, Andrey Repin wrote:
<snip>
It provide no information at all in any event (be it missing argument, or
nonexistent path (not like it's checking for existence right now... which only
making situation more complicated)), requiring non-obvious, manually conceived
tests to ensure that the program operates orderly.
I think you're looking for more from cygpath than it's designed to give.
Its intent is to perform direct Windows<->POSIX path conversions using the
mount table and to provide access to some system defined paths in Windows.
That's really it. It is not meant to validate input or output. If you have
a use case which requires that only valid paths are input to or output
from cygpath, that does need to be handled upstream or downstream.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple