Re^4: Does XCode 4 break Perl?

Replies are listed 'Best First'.
Re^5: Does XCode 4 break Perl? by Anonymous Monk on Apr 01, 2011 at 09:23 UTC
Doh O_RDONLY is supposed to come from Fcntl `$ perl -MFcntl=O_RDONLY -le " print +O_RDONLY " 0` [download] If you don't use Fcntl, there is no O_RDONLY constant	[reply] [d/l]
Re^6: Does XCode 4 break Perl? by Anonymous Monk on Apr 01, 2011 at 09:50 UTC
Yes, I'm aware of that. The point of this thread is that IO::AIO had no problems before the upgrade to XCode 4. At first glance it appears IO::AIO is sloppy in that it uses symbols without exporting them from Fcntl and POSIX, but I think it was working before because the XS code magically exported the symbols so they were available on the Perl side. After the upgrade, the mechanism that exported those symbols from XS to Perl appears to not work.	[reply]
Re^7: Does XCode 4 break Perl? by Anonymous Monk on Apr 01, 2011 at 09:54 UTC
So then you can add `use Fcntl...` to fix it, right?	[reply] [d/l]
Re^8: Does XCode 4 break Perl? by Anonymous Monk on Apr 01, 2011 at 10:09 UTC
Re^9: Does XCode 4 break Perl? by Anonymous Monk on Apr 01, 2011 at 10:26 UTC
Re^7: Does XCode 4 break Perl? by locked_user sundialsvc4 (Abbot) on Apr 01, 2011 at 17:17 UTC
Certainly you should go to Apple’s developer support sites and see if there are problem-reports concerning any impacts upon Perl (version??) as a consequence of XCode-4. It also seems to me that this problem, whatever it is, might be filled with a lot of red herrings. When words like “sloppy” crop up in conversation about fundamental production Perl code-libraries, my immediate instinct says, “do we truly understand this problem?” We might believe that we do, and might indeed be right, but warning-bells are going off right now that in similar situations I personally have jumped to utterly wrong conclusions. Everyone should be “from Missouri” now. Skeptically assume that the hypothesis isn’t correct, unless it can be demonstrated beyond doubt.