Hi all

I'm rewriting the library version discrimination, and am basing VC++ 7+ on Dinkumware's internal version symbol, _CPPLIB_VER. (FYI: It's located yvals.h)

I'm having trouble reproducing some reported aspects of a user's VC++ installation, and suspect that he has a different _CPPLIB_VER.

It'd be really helpful if you could each either:
* look up the #define in yvals.h, or
* compile and run the following program with your VC++ version (or versions,
if you've got more than one)

#include <iostream>
int main()
{
  std::cout << "_MSC_VER: " << _MSC_VER << std::endl;
  std::cout << "_CPPLIB_VER: " << _CPPLIB_VER << std::endl;
  return 0;
}

Many thanks in advance

Matt

-- 
-- 
Dr Matthew D. Wilson

Director - Synesis Software

m: +61 410 442244
t: +61 2 9399 9136
e: matthew@synesis.com.au
w: www.synesis.com.au

Synesis Software Pty Ltd

| Project Rescue | Software Team Management | Training | Software Architecture and Design | Custom Product Development | Solution Review |

This communication is confidential and may contain legally privileged information. If you are not the named recipient, please contact us immediately. You must not copy, use or disclose this communication, or any attachments or information in it, without our consent.

On 3/19/2010 5:22 AM, Matt Wilson wrote:
> #include<iostream>
> int main()
> {
>    std::cout<<  "_MSC_VER: "<<  _MSC_VER<<  std::endl;
>    std::cout<<  "_CPPLIB_VER: "<<  _CPPLIB_VER<<  std::endl;
>    return 0;
> }

Hi Matt,

prompt>cl /nologo /EHsc cpp-version.cpp & cpp-version.exe
cpp-version.cpp
_MSC_VER: 1400
_CPPLIB_VER: 405

Or do you only need VC7 variants?

Cheers,
Martin

Hi Mathew,

Microsoft Visual Studio 8

_MSC_VER: 1400
_CPPLIB_VER: 405

Microsoft Visual Studio 9.0

_MSC_VER: 1500
_CPPLIB_VER: 505

Microsoft Visual Studio 10.0 RC
_MSC_VER: 1600
_CPPLIB_VER: 520


BR,
Cláudio





Matt Wilson Wrote:

> Hi all
> 
> I'm rewriting the library version discrimination, and am basing VC++ 7+ on Dinkumware's internal version symbol, _CPPLIB_VER. (FYI: It's located yvals.h)
> 
> I'm having trouble reproducing some reported aspects of a user's VC++ installation, and suspect that he has a different _CPPLIB_VER.
> 
> It'd be really helpful if you could each either:
> * look up the #define in yvals.h, or
> * compile and run the following program with your VC++ version (or versions,
> if you've got more than one)
> 
> #include <iostream>
> int main()
> {
>   std::cout << "_MSC_VER: " << _MSC_VER << std::endl;
>   std::cout << "_CPPLIB_VER: " << _CPPLIB_VER << std::endl;
>   return 0;
> }
> 
> Many thanks in advance
> 
> Matt
> 
> -- 
> -- 
> Dr Matthew D. Wilson
> 
> Director - Synesis Software
> 
> m: +61 410 442244
> t: +61 2 9399 9136
> e: matthew@synesis.com.au
> w: www.synesis.com.au
> 
> Synesis Software Pty Ltd
> 
> | Project Rescue | Software Team Management | Training | Software Architecture and Design | Custom Product Development | Solution Review |
> 
> This communication is confidential and may contain legally privileged information. If you are not the named recipient, please contact us immediately. You must not copy, use or disclose this communication, or any attachments or information in it, without our consent.
> 
> 

"Martin Moene" <moene@eld.physics.LeidenUniv.nl> wrote in message news:4BA32E9C.5080406@eld.physics.LeidenUniv.nl...
> On 3/19/2010 5:22 AM, Matt Wilson wrote:
>> #include<iostream>
>> int main()
>> {
>>    std::cout<<  "_MSC_VER: "<<  _MSC_VER<<  std::endl;
>>    std::cout<<  "_CPPLIB_VER: "<<  _CPPLIB_VER<<  std::endl;
>>    return 0;
>> }
>
> Hi Matt,
>
> prompt>cl /nologo /EHsc cpp-version.cpp & cpp-version.exe
> cpp-version.cpp
> _MSC_VER: 1400
> _CPPLIB_VER: 405

Thanks, that's great!

> Or do you only need VC7 variants?

No. All versions of VC from 7 onwards (i.e. 7, 7.1, 8, 9 and 10)

Matt

Thanks Cláudio

May I ask one more question: is _IS_YES present in your VC++ 9's xstddef?

Matt

"Cláudio Albuquerque" <claudio.albuquerque@gmail.com> wrote in message news:ho02d3$2v3p$1@digitalmars.com...
> Hi Mathew,
>
> Microsoft Visual Studio 8
>
> _MSC_VER: 1400
> _CPPLIB_VER: 405
>
> Microsoft Visual Studio 9.0
>
> _MSC_VER: 1500
> _CPPLIB_VER: 505
>
> Microsoft Visual Studio 10.0 RC
> _MSC_VER: 1600
> _CPPLIB_VER: 520
>
>
> BR,
> Cláudio
>
>
>
>
>
> Matt Wilson Wrote:
>
>> Hi all
>>
>> I'm rewriting the library version discrimination, and am basing VC++ 7+
>> on
>> Dinkumware's internal version symbol, _CPPLIB_VER. (FYI: It's located
>> yvals.h)
>>
>> I'm having trouble reproducing some reported aspects of a user's VC++ installation, and suspect that he has a different _CPPLIB_VER.
>>
>> It'd be really helpful if you could each either:
>> * look up the #define in yvals.h, or
>> * compile and run the following program with your VC++ version (or
>> versions,
>> if you've got more than one)
>>
>> #include <iostream>
>> int main()
>> {
>>   std::cout << "_MSC_VER: " << _MSC_VER << std::endl;
>>   std::cout << "_CPPLIB_VER: " << _CPPLIB_VER << std::endl;
>>   return 0;
>> }
>>
>> Many thanks in advance
>>
>> Matt
>>
>> -- 
>> -- 
>> Dr Matthew D. Wilson
>>
>> Director - Synesis Software
>>
>> m: +61 410 442244
>> t: +61 2 9399 9136
>> e: matthew@synesis.com.au
>> w: www.synesis.com.au
>>
>> Synesis Software Pty Ltd
>>
>> | Project Rescue | Software Team Management | Training | Software Architecture and Design | Custom Product Development | Solution Review |
>>
>> This communication is confidential and may contain legally privileged information. If you are not the named recipient, please contact us immediately. You must not copy, use or disclose this communication, or any attachments or information in it, without our consent.
>>
>>
> 

Hi Matt,

Sorry for the delay in anwsering...but, better latter than never :-)

The _IS_YES is not defined in xstddef. Though, I was able to find it in the xtr1common file, but I think (not sure here) this file bellongs to the Visual C++ 2008 Feature Pack.

On the other hand VC++ 2010 has the _IS_YES defined in xstddef.

BR,
Cláudio


> Thanks Cláudio
> 
> May I ask one more question: is _IS_YES present in your VC++ 9's xstddef?
> 
> Matt
> 
> "Cláudio Albuquerque" <claudio.albuquerque@gmail.com> wrote in message news:ho02d3$2v3p$1@digitalmars.com...
> > Hi Mathew,
> >
> > Microsoft Visual Studio 8
> >
> > _MSC_VER: 1400
> > _CPPLIB_VER: 405
> >
> > Microsoft Visual Studio 9.0
> >
> > _MSC_VER: 1500
> > _CPPLIB_VER: 505
> >
> > Microsoft Visual Studio 10.0 RC
> > _MSC_VER: 1600
> > _CPPLIB_VER: 520
> >
> >
> > BR,
> > Cláudio
> >
> >
> >
> >
> >
> > Matt Wilson Wrote:
> >
> >> Hi all
> >>
> >> I'm rewriting the library version discrimination, and am basing VC++ 7+
> >> on
> >> Dinkumware's internal version symbol, _CPPLIB_VER. (FYI: It's located
> >> yvals.h)
> >>
> >> I'm having trouble reproducing some reported aspects of a user's VC++ installation, and suspect that he has a different _CPPLIB_VER.
> >>
> >> It'd be really helpful if you could each either:
> >> * look up the #define in yvals.h, or
> >> * compile and run the following program with your VC++ version (or
> >> versions,
> >> if you've got more than one)
> >>
> >> #include <iostream>
> >> int main()
> >> {
> >>   std::cout << "_MSC_VER: " << _MSC_VER << std::endl;
> >>   std::cout << "_CPPLIB_VER: " << _CPPLIB_VER << std::endl;
> >>   return 0;
> >> }
> >>
> >> Many thanks in advance
> >>
> >> Matt
> >>
> >> -- 
> >> -- 
> >> Dr Matthew D. Wilson
> >>
> >> Director - Synesis Software
> >>
> >> m: +61 410 442244
> >> t: +61 2 9399 9136
> >> e: matthew@synesis.com.au
> >> w: www.synesis.com.au
> >>
> >> Synesis Software Pty Ltd
> >>
> >> | Project Rescue | Software Team Management | Training | Software Architecture and Design | Custom Product Development | Solution Review |
> >>
> >> This communication is confidential and may contain legally privileged information. If you are not the named recipient, please contact us immediately. You must not copy, use or disclose this communication, or any attachments or information in it, without our consent.
> >>
> >>
> > 
> 
> 

Thanks Claudio

Matt

"Claudio" <claudio.albuquerque@gmail.com> wrote in message news:hqshr3$1idm$1@digitalmars.com...
> Hi Matt,
>
> Sorry for the delay in anwsering...but, better latter than never :-)
>
> The _IS_YES is not defined in xstddef. Though, I was able to find it in the xtr1common file, but I think (not sure here) this file bellongs to the Visual C++ 2008 Feature Pack.
>
> On the other hand VC++ 2010 has the _IS_YES defined in xstddef.
>
> BR,
> Cláudio
>
>
>> Thanks Cláudio
>>
>> May I ask one more question: is _IS_YES present in your VC++ 9's xstddef?
>>
>> Matt
>>
>> "Cláudio Albuquerque" <claudio.albuquerque@gmail.com> wrote in message news:ho02d3$2v3p$1@digitalmars.com...
>> > Hi Mathew,
>> >
>> > Microsoft Visual Studio 8
>> >
>> > _MSC_VER: 1400
>> > _CPPLIB_VER: 405
>> >
>> > Microsoft Visual Studio 9.0
>> >
>> > _MSC_VER: 1500
>> > _CPPLIB_VER: 505
>> >
>> > Microsoft Visual Studio 10.0 RC
>> > _MSC_VER: 1600
>> > _CPPLIB_VER: 520
>> >
>> >
>> > BR,
>> > Cláudio
>> >
>> >
>> >
>> >
>> >
>> > Matt Wilson Wrote:
>> >
>> >> Hi all
>> >>
>> >> I'm rewriting the library version discrimination, and am basing VC++
>> >> 7+
>> >> on
>> >> Dinkumware's internal version symbol, _CPPLIB_VER. (FYI: It's located
>> >> yvals.h)
>> >>
>> >> I'm having trouble reproducing some reported aspects of a user's VC++ installation, and suspect that he has a different _CPPLIB_VER.
>> >>
>> >> It'd be really helpful if you could each either:
>> >> * look up the #define in yvals.h, or
>> >> * compile and run the following program with your VC++ version (or
>> >> versions,
>> >> if you've got more than one)
>> >>
>> >> #include <iostream>
>> >> int main()
>> >> {
>> >>   std::cout << "_MSC_VER: " << _MSC_VER << std::endl;
>> >>   std::cout << "_CPPLIB_VER: " << _CPPLIB_VER << std::endl;
>> >>   return 0;
>> >> }
>> >>
>> >> Many thanks in advance
>> >>
>> >> Matt
>> >>
>> >> -- 
>> >> -- 
>> >> Dr Matthew D. Wilson
>> >>
>> >> Director - Synesis Software
>> >>
>> >> m: +61 410 442244
>> >> t: +61 2 9399 9136
>> >> e: matthew@synesis.com.au
>> >> w: www.synesis.com.au
>> >>
>> >> Synesis Software Pty Ltd
>> >>
>> >> | Project Rescue | Software Team Management | Training | Software Architecture and Design | Custom Product Development | Solution Review |
>> >>
>> >> This communication is confidential and may contain legally privileged information. If you are not the named recipient, please contact us immediately. You must not copy, use or disclose this communication, or any attachments or information in it, without our consent.
>> >>
>> >>
>> >
>>
>>
>