Re^7: Getting the absolute path of a script, without PWD (bug)

Please, you should really file a bugreport against Cwd.

Maybe they can't fix cwd() b/c of backwards compatibility but should at least clarify the documentation.

From my POV it's already silly to call two different routines getcwd() and cwd()

So you could suggest to add a new pwd() which always does something like `pwd -L`

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re^7: Getting the absolute path of a script, without PWD (bug) Select or Download Code

Replies are listed 'Best First'.
Re^8: Getting the absolute path of a script, without PWD (bug) by perlancar (Hermit) on Jul 16, 2021 at 10:30 UTC
Maybe after I'm more knowledgeable about the actual differences between `getcwd()` and `cwd()`. Right now, it's not clear that `cwd()` should be "fixed". `getcwd()` tries to call `getcwd(3)` or reimplements it, while `cwd()` makes no such promise. And this statement is not strictly wrong: "For most systems it is identical to `pwd` (but without the trailing line terminator)." Though it might benefit the reader to be aware of the difference between `pwd -P` and `pwd -L`, and which one the reader is getting with `pwd`.	[reply]
Re^9: Getting the absolute path of a script, without PWD (bug) by LanX (Saint) on Jul 16, 2021 at 10:43 UTC
Perl should ideally have predictable and consistent behavior across all plattforms and not depend on some shell settings. Alone the fact that termux acts differently to ubuntu should ring the alarm bell ... Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]