> Shouldn't that be "."?
>
> > append_filename("a", "") = ""
>
> "a"
Umm. Don't think so. At least it will be that
way until you convince me that it must be
another way
>
> What about
>
> append_filename("", "b") ?
>
> Would that be an error?
No. It's okay. I just forgot to mention that case.
append_filename("", "b") will produce "b"
> concat_dirnames("/foo", "/bar") = error?
> concat_dirnames("foo", "/bar") = error?
> concat_dirnames("/foo", "bar") = "/foo/bar"
I just want to remind you the Leo's words:
"Please keep in mind, that the intended usage inside Parrot just should
be to locate some standard include or extension files for Parrot
internals. More abstraction and complexity can always be added above
that or implemented by HLLs." -- Him.(~:)
I don't suppose Leo will be pass in spoiled data.
> > MS Win32
> > ==========
> > append_filename(".", "") = ""
>
> "."
No.
> > append_filename("a", "") = ""
>
> "a"?
Still no.
> What about volumes?
I plan a special functions for volumes, and nodes,
and root dirs like prepend_volume, prepend_node,
prepend_rootdir.
For example, prepend_rootdir could throw the
"prepend_rootdir is unsupported on this platform"
exception on windows. Of course, I will go implement
those if Parrot needs those.
