in reply to Re^2: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker
in thread Clean smoke-test install for Inline based modules using Inline::MakeMaker
Thanks for that report. That has to be an Inline::CPP issue, so a separate problem. syphilis and I thought we had solved it a couple weeks ago, but it looks like more attention is required. I'll get to work on it. You must be in the 7% that are still having problems with Inline::CPP. My goal there is to get that module to the point that it installs for all systems that Inline::C installs for (assuming they have a C++ compiler), which would be about 98%.
More details: The problem is related to how C++ has evolved and standardized. As I'm sure you know better than I, before a standard was adopted C++ headers usually had the .h extension. More recently (which really isn't all that recent now) C++ standardized around headers without the .h extension. Inline::CPP automatically includes <iostream>, or <iostream.h>. It's supposed to detect which is required, and for the majority of systems it seems to get it right. It looks like in your case it's guessing wrong. Now that I know it's still an issue I can turn my sights on it again. It's enough of a sore-spot that I'm almost inclined to eliminate the automatic inclusion of <iostream>, but that wouldn't really solve the problem of distributing code based on Inline::CPP, as it just forces module authors to try to figure out how to decide between '.h' or no '.h' themselves.
Dave
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker
by BrowserUk (Patriarch) on Dec 15, 2011 at 19:35 UTC | |
by davido (Cardinal) on Dec 15, 2011 at 20:05 UTC | |
by BrowserUk (Patriarch) on Dec 15, 2011 at 21:08 UTC | |
by davido (Cardinal) on Dec 15, 2011 at 21:19 UTC |