Re: Multibyte and unibyte file names

[Stefan Monnier]

>> At least I disagree with your Ffile_name_directory suggestion: if the
>> file-name is already encoded and it results in bugs, the fix should be
>> in the caller.
> So you are saying these primitives should assume decoded file names,
> and if called with encoded ones, exhibit undefined behavior, for which
> the fix is in the caller, is that right?

Pretty much, yes.


        Stefan