use Perl

• Strongly, strongly disagree (Score:1)

  by ChrisDolan (2855)

  You're way off base on this one.

  I've been using Mac for Perl dev for about 6-7 years (whenever OS X 10.1 came out) and consider it first class. The Mac:: packages are largely irrelevant -- Carbon is a legacy API from the 90s, about as relevant today as a Win95-specific API would be I suppose. If you used a Win95:: library, you'd get similar complaints from users of a modern Windows OS.

  The "flood" of Win32:: packages is because you need those platform-specific hacks to get anything done on Windows Perl. N
  • Re: (Score:2)

    by Ovid (2709)

    File::HomeDir, for the Mac, requires Mac::Files which is unfortunately bundled with Mac::Carbon. The latter does not and will never run on a 64-bit Perl, but that's the direction we're going. Because Bundle::CPAN requires File::HomeDir, a fresh Perl installation on a Mac is very painful if you have a 64-bit Perl. I had to manually install File::HomeDir after locally patching it to work around the Mac::Files pain.
    • Re: (Score:1)

      by Alias (5735)

      Then build me a Cocoa replacement and I'll link to that instead
      • Re: (Score:2)

        by Ovid (2709)

        But you don't need Cocoa or Carbon just to have File::HomeDir functionality, do you? Or am I missing something?
        • Re: (Score:1)

          by Alias (5735)

          See my previous comments.

          The location of your "Documents" directory can only be determined via a system call. You cannot assume ~/Documents in all cases.

          This is the reason that we use Mac::Files in the first place.
          • Re:Strongly, strongly disagree (Score:2)

            by drhyde (1683) on 2009.10.10 15:42 (#70840) Homepage Journal

            Surely, on OS X, "my Documents" is always ~/Documents. Cos I'm damned if I can see a way of changing where it is.

            Reply to This

            Parent