Re: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Phlip <pl...@sy...>]

RE: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' =
failure time?[can we configure this mail server to Reply to the group, =
not the individual? This lets us archive the technical discussions.]=20
  From: Kyle Brost=20
  It seems as though you are doing a lot of work to embed PerlUnit=20
  into your development environment when you don't have to.  There=20
  is another project called CppUnit that would save you a lot of time=20
  and headache.=20

Well, when I got here the shop was absolutely naive to Programmer Tests, =
but they correctly worship their "customer acceptance tests" on the =
server of their product. At the same time I'm too green here to just =
order everyone to comprehend CppUnit's myriad riddles.

So, I downloaded CppUnit, copied their example.cpp into this project, =
and got it to compile >without< CppUnit or all the crud that package =
inexplicably drags along with it. (Legacy of Java legacy of Smalltalk, =
etc.)

I plopped the result here - it's just one header file:

http://www.c2.com/cgi/wiki?VisualCeePlusPlus

It uses the filename(linenumber) -> OutputDebugString trick that lets =
you navigate thru errors or debug traces by tapping <F4> too.

However, this site has a huge investment in Perl scripts to test their =
server, so I am bonding Perl with VC++ so I can then run all those =
scripts thru the GUI instead of the server. I want to see if I can run =
it until smoke rises from it.

But first, their elaborate Perl scripts are screaming for a good =
refactor party first, so...

--=20

Phlip