Re: write-region bug ?

[Stefan Monnier]

>> >   (write-region 1 1024 "foo")
>> >   (write-region "\nEnd-of-foo\n." nil "foo" t t)
>> 
>> Which is just as naturally written:
>>
>>     (write-region 1 1024 "foo" nil t)
>>     (write-region "\nEnd-of-foo\n." nil "foo" t)
>
> But that doesn't make the former illegitimate.

It's not a legitimate *need*.  It's a use that happens to work, but it
doesn't show a use-case where you *need* this odd corner case.
So, I'm still at the same point as before: I can imagine existing code
which happens to use this behavior, but not code which needs
this behavior.

> So I don't see any reason to declare it unsupported.

It's simply to try and help users not to shoot themselves in the foot.
I know we usually don't try very hard, so it's not crucial.


        Stefan