David James wrote:
> On 11/5/05, Erik Huelsmann <ehuels@gmail.com> wrote:
>
>>> (If someone on Windows uses a diff tool that can't handle a NUL: as a
>>> file name, they can write a wrapper for it. I don't think we should
>>> cater to every half-ported utility in the world.)
>>>
>> Great! Well, I was already planning to use SVN_NULL_DEVICE_NAME (but
>> was looking in the wrong place: APR). Glad we have even discussed it
>> now and having been pointed in the right direction.
>>
>> Consider it implemented!
>>
> Is it possible to implement this behaviour without breaking external diff tools?
>
As I said, any properly implemented external diff tool should do the
right thing with "NULL:" -- if it doesn't, it's broken already. We could
create an empty file before calling an external tool with a "NULL:" file
name argument and replacing the name, but I don't think we should bother.
A Windows app that doesn't handle " NUL:" correctly is as broken as one
that can't tell the difference between "C:foo.txt" and "C:\foo.txt". I
suspect this will only happen in tools that have been ported to Windows
from (usually) Unix -- and whoever ported it can fix the bug. Not to
mention that there's a really trivial workaround.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 5 18:31:00 2005