Are perl header file names worth being "unpolluted"?

I recently found out that perl has a header file that conflicts with
the (soon to be) newest version of the `Curses' module.  (The file in
question is "form.h".)  I can work around it (by inserting a
`-I/usr/include' into the appropriate spot), but I thought I'd ask if
it was worth unpolluting the header file namespace.

So, does anyone feel strongly about this one way or other?


William

• Are perl header file names worth being "unpolluted"? by William Setzer
• Re: Are perl header file names worth being "unpolluted"? by Jarkko Hietaniemi