Geek asks and answers

C ++ codebase rewrite from MFC to * nix

I work in the company for the summer, and I have to look at different ways to look at the current code base (C ++, MFC, about 100 thousand lines) and use state machines to simulate the current program.

I read a couple of articles, and CPP2XMi looks like it might be useful to try to build sequence diagrams as a start.

The ultimate goal is to evaluate the possibility of switching from microsoft as O / S and look at the development (possibly in another language) of * nix.

I also began to study the dependencies of MFC to see if you can just port the current code to C ++.

I had a program that works through WINE and in terms of performance, it seems acceptable, but I still need to explore other solutions, since it will only work on X86, while we have other solutions running on MIPS and ARM.

Any other ideas or comments that I could pay attention to?

+3
source share
4 answers

The first thing I would look at is where to use mfc and other non-portable things. If the only place where mfc is is in the interface layer, for example, you can isolate the work.

, fesablity , . , , , . , MFC Nix - . - , Windows.

+1

wxWidgets MFC. .

+1

, GUI . MFC , CString, GUI-.

, MFC GUI , , , .

, , , , , . , , , , . , , .

, wxWidgets Qt.

MFC, wxWidgets, . , Borland OWL MFC, . ; . , . , , Visual ++ Professional Express, MFC. V++ Professional ( ), MFC.

+1

I once ported a large COM library from MFC to portable code. I used STL and boost to replace all MFC bits. For example, CString => std :: string and VARIANT => boost :: any .

It took forever, but it was basically a simple replacement and setup. Fortunately, it had no gui code - it was a data processing library.

0
source

More articles:


All Articles