Re: [PATCH, take 3][cygwin|mingw] Control where win32 DLLs get installed.

2009-08-14 Thread Dave Korn
Ralf Wildenhues wrote: So I guess we need to stick to host matching in the code, Shame, but at least it makes my life slightly easier ;-) Still finishing it off and getting it tested, but while that's going, here's a preview of the path canonicalisation function as I've got it so far; let

Re: [PATCH, take 3][cygwin|mingw] Control where win32 DLLs get installed.

2009-08-14 Thread Dave Korn
Eric Blake wrote: Cancelling out .. is wrong for 'symlink/..', when symlink does not necessarily point to a working directory exactly one level down. (True, cygwin does not implement POSIX semantics here, and cancels out foo/.. behind your back rather than properly resolving foo, but this

Re: [PATCH, take 3][cygwin|mingw] Control where win32 DLLs get installed.

2009-08-14 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dave Korn on 8/14/2009 5:34 AM: Still finishing it off and getting it tested, but while that's going, here's a preview of the path canonicalisation function as I've got it so far; let me know if I've done any major no-nos please!

Re: [PATCH, take 3][cygwin|mingw] Control where win32 DLLs get installed.

2009-08-14 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dave Korn on 8/14/2009 7:11 AM: a=`` is non-portable, but can always be replaced by the portable: a=`` See why I don't like spurious around variable assignments? Ah, now I do. Ok, but is some nice clear list of where you

Re: [PATCH, take 3][cygwin|mingw] Control where win32 DLLs get installed.

2009-08-14 Thread Dave Korn
Eric Blake wrote: I think it's as simple as: And beyond that, it's just lots of practice. I agree that it often feels like you have to memorize loads of information to write portable shell, but at least these public reviews catch a lot of the pitfalls. Your cheat sheet will come in very