Given that the perl community (in general) frowns so heavily upon warnings being emitted at *any* stage, it's rather surprising that this sort of thing is tolerated.I never got the impression p5p is really concerned about bending code backwards just to avoid warnings. They are *warnings* after all. And there are (C) compilers that are picky. Very, very picky (they are C compilers, so they can spend time on nitpicking). Combine that with the fact the perl sources need to compile on a wide range of compilers, compiler versions, platforms and OSses, and it contains code that has been written eons ago. I'd very surprised if there are many compiler/OS/platform combinations that doesn't emit a single warning during the perl build process.
In reply to Re^11: Perl 5.12.0 has been released! (exetype problem 64-bit)
by JavaFan
in thread Perl 5.12.0 has been released!
by ikegami
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |