in reply to Re^5: Darwin and File::HomeDir
in thread Darwin and File::HomeDir

What are you talking about? The user shouldn't have to even know that File::HomeDir is being used by one of his scripts, much less possess some "common knowledge" about it.

If you think that, then why you suggest a patch for File::HomeDir documentation?

The user being discussed in this thread is the code writer who writes

use File::HomeDir;
and then his code breaks because File::HomeDir returns a path with spaces in it.

File::HomeDir is working as designed. There is no bug in File::HomeDir.

Replies are listed 'Best First'.
Re^7: Darwin and File::HomeDir
by ikegami (Patriarch) on May 21, 2011 at 16:48 UTC

    The user being discussed in this thread is the code writer who writes

    Actually, no. I'm the only one who used the term, and I was referring to the user the of the script.

    If you think that, then why you suggest a patch for File::HomeDir documentation?

    To try to avoid the creation of buggy modules.

    File::HomeDir is working as designed. There is no bug in File::HomeDir.

    That's what I said.I agree, I never said there was.

      If you believe that, then what was all that stuff about imposing limits on users? You're switching your argument midstream, just to keep the thread going.

        I never thought there was a bug in File::HomeDir, and I never said I did. I said the only thing that can be done is to add a warning to File::HomeDir's documentation, and that anything else would have detrimental effects or would be near impossible.