[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dist-obj] Sourcesafe to CVS migration, C++ GC

Hi, Ron: Interesting problem. But wrt. the kind of application you are
talking about I've had much success w/ Purify/Quantify and extended
testing -- w/ real stressers. The idea is to write a 'feed simulator'
and 'feed logger' -- you run the latter on the real feed over say 2
weeks and create lots of files :). Then you run the simulator at say 10
times real-time so you can stress test your app. much faster than you
could connected to the real feed. 

I have found that if you rely on GC strategies programmers get lazy
and it will come back to haunt you.. have a 'memory mgmt' discussion
w/ them early on, and wrap a thin layer around heap calls.. so you can
redirect them, log them etc. Purify also helps a great deal in this
regard. (Also note that GC in the app. can behave really weirdly
wrt. thread semantics and exception handling.. you may want to read
the various Win32 vs. Linux critiques on the Web in this
regard. GCC/g++ like tools are notorious wrt. exception handling in my
experience).

Just my $.02 cents.

ps. I don't want to say bad things about Nu-mega, but Boundschecker is
a big waste of time on large projects. I suppose it's ok for
small/medium projects, but it hasn't worked out well for us on certain
large projects. Purify/Quantify do work, but they have become somewhat
expensive since Rational acquired them. 


==========================================================================
To manage your subscription, mailto:dist-obj-help@distributedcoalition.org 
Archives, FAQ, etc.     http://www.distributedcoalition.org/mailing_lists/