Re: mfc pitfalls
- From: "jmarc" <jmarc@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 01 Feb 2007 19:32:52 GMT
There are many styles of programming.
Each may vary a lot from one to another,
but not because one or the other is badly
implemented.
You should have defined the programming
style you want, or those you'l be easy with
afterward, before contracting the outsource.
A source code may be very well implemented,
but hard to be understood by someone who
don't know much about MFC tricks.
Finally, my opinion is that you should be
able to understand the design of the imple-
mentation the outsouce have been followed.
To achive that, I really think the outsource
should be able to provide you at least few
UML diagrams.
.... all the class he does implement should be
covered somewhere..
For my part, I also like controling all the
graphical resource ID numbers defined in
a project, and their naming, at all time
during the implementation.
It might be surprising, but I also avoid the
use of warning popup, and never use
Try and Catch method. I try to build
applications to stay up and running all
the possible time.
I highly prefer using a Logger in my framework,
(all situation should be handle), along with a
good Tracer that can be unlock to catch
problems in the field later, if any still undiscovered
during the test phase.
... At least.. Uncommented code might be
a very good hint about that outsource!
jmarc..
"telepet9" <telepet9@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:32AD356D-F048-4798-9CF6-DA5709CCD092@xxxxxxxxxxxxxxxx
Hi,
I need to review code from our outsourcing.
I have some experience with MFC but not to the extant that I can easilly
identify potential problems.
So, can you give me some pointers on what from your experience should be
avoided while programming using MFC. ( We trying to make the outsourcing
to
provide us code that will be easy to maintain/debug )
Thank you in advance.
.
- Follow-Ups:
- Re: mfc pitfalls
- From: Joseph M . Newcomer
- Re: mfc pitfalls
- Prev by Date: Re: macros and preprocessor
- Next by Date: Re: Problem with modal dialogs
- Previous by thread: Problem in Resource copy ...
- Next by thread: Re: mfc pitfalls
- Index(es):
Relevant Pages
|
Loading