First thought: if it ain't broken, don't fix it. Did anybody complain? Well, that's only a first thought...

@erco77 wrote:

Not a bug, since the docs don't say one way or the other what style it returns.

I agree.

However, I think the caller might want to choose.

Why? Serious. I think there are two points:

1. Many of the Windows API functions allow both front and back slashes. If not, please correct me.
2. If this would have been an issue in the past we'd have seen more "complaints" by users.

I'm always for fixing bugs, and if it's possible, make code and behavior consistent. But if we don't know what the correct behavior is, what can we do?

I think we should try to avoid inconsistencies (and bugs for sure) as far as possible but leave everything else as-is unless it's really easy to fix. I don't think that adding a user option to decide what behavior they want is not "really easy", particularly if this would have to be added to "ALL fltk functions dealing with paths" as you wrote above.

OTOH, if there's a volunteer and the API is simple and hopefully backwards compatible and (what else) ... I wouldn't object but I also wouldn't (be able to) contribute much.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.