The test in Inline::CPP.pm is 

    my $iostream = "iostream";
#    $iostream .= ".h" unless $o->{ILSM}{STD_IOSTREAM};
    if($o->{ILSM}{MAKEFILE}{CC} =~ /^cl/) { 
        $iostream .= ".h" 
            unless $o->{ILSM}{STD_IOSTREAM}; 
    }
    $o->{ILSM}{AUTO_INCLUDE} =~ s|%iostream%|$iostream|g;

[download]

Ie. If the compiler command is 'cl' append '.h'. But, according to MS, all their compilers since VS 2003 now only supply the newer standard extension-less standard header files.

I have Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64 which I memory serves equates to VS 2008; internal version 9; File format version 10. (Damn I wish they'd use ONE bloody name for things!), so I think the above test will need to be more selective.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

In reply to Re^4: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker by BrowserUk
in thread Clean smoke-test install for Inline based modules using Inline::MakeMaker by davido

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.