@kas1e

It just helps out if a bash shell script or something calls curl when building some program. I've never seen that happen, but lets say for example you downloaded some Python program that used curl and unix paths. It's just better in my opinion to maintain that compatibility. It doesn't bloat it at all.

Also, if a program or game uses libcurl with local files, it'll expect unix paths. Though, generally in those cases I modify the game to use Amiga paths.

Quote:

Just be sure that should be file:///work:aaa , or file://localhost/work:aa - that is necessary ones, if other ones will works - why not, but those 2 are must.

Of course.

After reading the wikipedia link about the File URI scheme, I understand how the 3 slashes works. I was just assuming that the 3rd slash was infact the start of the file path after file://, but the article continued on and showed how 3 slashes is still used even on Windows, like file:///c:/WINDOWS/clock.avi

Also, i'm not sure if you were trying to say that the unix paths should still be working after applying the Amiga patches or not. I was pointing out that the Amiga patch you provided above actually breaks the regular unix-path functionality by always removing the slash if it is the first character.

My tweak makes it compatible both ways. Essentially it tries opening it parsing the path as an Amiga style path, and if it can't, it parses it as a unix style path.

Last edited by MickJT on 17-May-2011 at 09:34 PM.
Last edited by MickJT on 17-May-2011 at 09:32 PM.
Last edited by MickJT on 17-May-2011 at 09:27 PM.

Locking this thread, discussion continues

here in part 2.

Nice to see a long thread in the OS4 forum, usually only happens in "free for all"

_________________
Site admins are people too..pooff!