cppunit-devel

[Cppunit-devel] msvc7 support

[Andrey M. <mel...@si...>]

Hello

I created VC7Outputter class to match format expected by Visual
Studio.NET (see VC7Outputter.h in attached ZIP file). The class require
CompilerOutputter::m_stream to be protected instead of private, so don't
forget to modify CompilerOutputter.h

Also it seems there are no valid config for VC++ 7. How can I help with
them?

Compiler detection: #if _MSC_VER >= 1300 (VC6 had _MSC_VER > 1000)
Output format: #define CPPUNIT_COMPILER_LOCATION_FORMAT "%p(%l): error :
" (VC7 had simply "%p(%l): "

Messages in VC6 format are also parsed and clickable in VC7, but they
don't appear in Tasks window, only in Output window.

Also all CPPUnit classes are put in global namespace despite namespases
are supported and CPPUNIT_HAVE_NAMESPACES is defined.

Can somebody try to compile the attached project in Visual Studio .NET
and see if the new class is better than we have now with
CompilerOutputter?

Andrey

Re: [Cppunit-devel] msvc7 support

[Baptiste L. <gai...@fr...>]

Thanks. I've made the necessary change to the msvc config header. It's now
in the CVS.

How did you get the 'namespace' bug. I have switched a project to VS 7
recently (rfta of http://cpptool.sf.net) and it compiles correctly, and it
contains explicit reference to the CppUnit namespace.

By the way (I'm a VS newbie), is there a way to get VS to show you the task
error detail other than clicking on the output pane or using the tooltip ?

Baptiste.

----- Original Message ----- 
From: "Andrey Melnikov" <mel...@si...>
To: <cpp...@li...>
Sent: Wednesday, May 14, 2003 9:29 PM
Subject: [Cppunit-devel] msvc7 support


> Hello
>
> I created VC7Outputter class to match format expected by Visual
> Studio.NET (see VC7Outputter.h in attached ZIP file). The class require
> CompilerOutputter::m_stream to be protected instead of private, so don't
> forget to modify CompilerOutputter.h
>
> Also it seems there are no valid config for VC++ 7. How can I help with
> them?
>
> Compiler detection: #if _MSC_VER >= 1300 (VC6 had _MSC_VER > 1000)
> Output format: #define CPPUNIT_COMPILER_LOCATION_FORMAT "%p(%l): error :
> " (VC7 had simply "%p(%l): "
>
> Messages in VC6 format are also parsed and clickable in VC7, but they
> don't appear in Tasks window, only in Output window.
>
> Also all CPPUnit classes are put in global namespace despite namespases
> are supported and CPPUNIT_HAVE_NAMESPACES is defined.
>
> Can somebody try to compile the attached project in Visual Studio .NET
> and see if the new class is better than we have now with
> CompilerOutputter?
>
> Andrey
>

RE: [Cppunit-devel] msvc7 support

[Andrey M. <mel...@si...>]

Fortunately, "Namespace" bug was in Visual Studio IDE, not in CppUnit
itself. class ExampleTestCase : public CppUnit::TestCase compiles fine,
but IDE claims that the namespace doesn't exist, and doesn't want to
suggest list of classes when you type "CppUnit::". I think this is a bug
in Intellisense subsystem of IDE (Intellisense provides autocompletion
for identifiers, shows tooltip with declaration of identifier etc). 

Andrey

-----Original Message-----
From: cpp...@li...
[mailto:cpp...@li...] On Behalf Of Baptiste
Lepilleur
Sent: Thursday, May 15, 2003 9:42 AM
To: cpp...@li...
Subject: Re: [Cppunit-devel] msvc7 support


Thanks. I've made the necessary change to the msvc config header. It's
now in the CVS.

How did you get the 'namespace' bug. I have switched a project to VS 7
recently (rfta of http://cpptool.sf.net) and it compiles correctly, and
it contains explicit reference to the CppUnit namespace.

By the way (I'm a VS newbie), is there a way to get VS to show you the
task error detail other than clicking on the output pane or using the
tooltip ?

Baptiste.

----- Original Message ----- 
From: "Andrey Melnikov" <mel...@si...>
To: <cpp...@li...>
Sent: Wednesday, May 14, 2003 9:29 PM
Subject: [Cppunit-devel] msvc7 support


> Hello
>
> I created VC7Outputter class to match format expected by Visual 
> Studio.NET (see VC7Outputter.h in attached ZIP file). The class 
> require CompilerOutputter::m_stream to be protected instead of 
> private, so don't forget to modify CompilerOutputter.h
>
> Also it seems there are no valid config for VC++ 7. How can I help 
> with them?
>
> Compiler detection: #if _MSC_VER >= 1300 (VC6 had _MSC_VER > 1000) 
> Output format: #define CPPUNIT_COMPILER_LOCATION_FORMAT "%p(%l): error

> : " (VC7 had simply "%p(%l): "
>
> Messages in VC6 format are also parsed and clickable in VC7, but they 
> don't appear in Tasks window, only in Output window.
>
> Also all CPPUnit classes are put in global namespace despite 
> namespases are supported and CPPUNIT_HAVE_NAMESPACES is defined.
>
> Can somebody try to compile the attached project in Visual Studio .NET

> and see if the new class is better than we have now with 
> CompilerOutputter?
>
> Andrey
>



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

Re: [Cppunit-devel] msvc7 support

[Baptiste L. <gai...@fr...>]

Glad to hear that it was just the intellisense getting confused (probably by
the CPPUNIT_NS macro).

I've made a new unoffical tar ball. You can get it at:
http://cppunit.sourceforge.net/snapshot/cppunit-1.9.11-portability-test3.tar.gz

Notes that you can also obtain a daily backup of the cvs repository at:
http://cvs.sourceforge.net/cvstarballs/cppunit-cvsroot.tar.gz

(this works for most of sf projects).

Baptiste.

----- Original Message ----- 
From: "Andrey Melnikov" <mel...@si...>
To: <cpp...@li...>
Sent: Friday, May 16, 2003 2:32 PM
Subject: RE: [Cppunit-devel] msvc7 support


> Fortunately, "Namespace" bug was in Visual Studio IDE, not in CppUnit
> itself. class ExampleTestCase : public CppUnit::TestCase compiles fine,
> but IDE claims that the namespace doesn't exist, and doesn't want to
> suggest list of classes when you type "CppUnit::". I think this is a bug
> in Intellisense subsystem of IDE (Intellisense provides autocompletion
> for identifiers, shows tooltip with declaration of identifier etc).
>
> Andrey
>
> -----Original Message-----
> From: cpp...@li...
> [mailto:cpp...@li...] On Behalf Of Baptiste
> Lepilleur
> Sent: Thursday, May 15, 2003 9:42 AM
> To: cpp...@li...
> Subject: Re: [Cppunit-devel] msvc7 support
>
>
> Thanks. I've made the necessary change to the msvc config header. It's
> now in the CVS.
>
> How did you get the 'namespace' bug. I have switched a project to VS 7
> recently (rfta of http://cpptool.sf.net) and it compiles correctly, and
> it contains explicit reference to the CppUnit namespace.
>
> By the way (I'm a VS newbie), is there a way to get VS to show you the
> task error detail other than clicking on the output pane or using the
> tooltip ?
>
> Baptiste.
>
> ----- Original Message ----- 
> From: "Andrey Melnikov" <mel...@si...>
> To: <cpp...@li...>
> Sent: Wednesday, May 14, 2003 9:29 PM
> Subject: [Cppunit-devel] msvc7 support
>
>
> > Hello
> >
> > I created VC7Outputter class to match format expected by Visual
> > Studio.NET (see VC7Outputter.h in attached ZIP file). The class
> > require CompilerOutputter::m_stream to be protected instead of
> > private, so don't forget to modify CompilerOutputter.h
> >
> > Also it seems there are no valid config for VC++ 7. How can I help
> > with them?
> >
> > Compiler detection: #if _MSC_VER >= 1300 (VC6 had _MSC_VER > 1000)
> > Output format: #define CPPUNIT_COMPILER_LOCATION_FORMAT "%p(%l): error
>
> > : " (VC7 had simply "%p(%l): "
> >
> > Messages in VC6 format are also parsed and clickable in VC7, but they
> > don't appear in Tasks window, only in Output window.
> >
> > Also all CPPUnit classes are put in global namespace despite
> > namespases are supported and CPPUNIT_HAVE_NAMESPACES is defined.
> >
> > Can somebody try to compile the attached project in Visual Studio .NET
>
> > and see if the new class is better than we have now with
> > CompilerOutputter?
> >
> > Andrey