Funny Post on MFC
-
That's not funny; that's painfully true.
Now taking suggestions for the next release of CPhog...
Yeah but MFC laughs in your face every morning... ;)
-
Yeah but MFC laughs in your face every morning... ;)
-
It mocks me. It mocks me.
Now taking suggestions for the next release of CPhog...
Indeed. MFC's message maps is the mother of all mockers. I wish I had written all this code in ATL so long ago... :sigh: Anyone up for charity work - porting a boatload of MFC to ATL. Will provide food and housing. :) No more MFC crap for me for the rest of this week. Time to go home!
-
Indeed. MFC's message maps is the mother of all mockers. I wish I had written all this code in ATL so long ago... :sigh: Anyone up for charity work - porting a boatload of MFC to ATL. Will provide food and housing. :) No more MFC crap for me for the rest of this week. Time to go home!
I know what you mean. The worst is, I understand the stuff, but hate being the one to maintain it. This, more than anything, is probably what's driving me to using HTML+JS in our desktop UI - other people can mess with it, and i don't have to worry about horrible things happening as a result.
Now taking suggestions for the next release of CPhog...
-
Indeed. MFC's message maps is the mother of all mockers. I wish I had written all this code in ATL so long ago... :sigh: Anyone up for charity work - porting a boatload of MFC to ATL. Will provide food and housing. :) No more MFC crap for me for the rest of this week. Time to go home!
I'll do it.
-
I'll do it.
-
I found the following quote from one person(in slashdot) as funny "The vision of MFC: Let's saddle people with the extra intellectual mass of C++, but ignore the language's most powerful features; instead we'll fill in the gaps with a bunch of C preprocessor macros. Then we'll throw in a bunch of wizards to encourage people to automatically generate spaghetti boilerplate by the megabyte." I know when Microsoft started developing MFC, templates were not really mature (compliers not implemented them fully)... -Madhu -- modified at 10:32 Friday 17th March, 2006
I actually like MFC... ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
Sometimes. It generally depends on what I am doing. If it interests me I will eat very little. But for a general rule of thumb, take what you eat, multiply by three.
-
Indeed. MFC's message maps is the mother of all mockers. I wish I had written all this code in ATL so long ago... :sigh: Anyone up for charity work - porting a boatload of MFC to ATL. Will provide food and housing. :) No more MFC crap for me for the rest of this week. Time to go home!
:laugh: Funny that. I keep looking at the ResOrg source and thinking "WTL 7.5.... :rolleyes: Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
I actually like MFC... ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
I really liked it until I got used to the WTL way of doing things (in particular adding functionality through mix-in classes rather than inheritance). The message map architecture is also much more flexible in ATL/WTL, although you don't get automatic command routing for free (still one of MFC's best features, in my opinion). The downside is usually compilation time of course. Templates have their price...but I'm finding for most small to medium size projects (say up to about 100,000 lines) it's a price worth paying. Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
I think it is a beauty that MFC code developed in Visual C++ 1.5 still survives in MFC 8.0 (with some changes ofcourse).
It's quite a feat, that's for certain. The level of backward compatibility in MFC (even at the binary level) is truly incredible...quite an achievment by any standards. Of course, it comes at a price...many things (among them some of MFC's best and worst features) are set in stone... Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
Jörgen Sigvardsson wrote:
Do you eat a lot?
What is the problem? Isn't "smorgasbord" a Swedish thing? :laugh:
-
I really liked it until I got used to the WTL way of doing things (in particular adding functionality through mix-in classes rather than inheritance). The message map architecture is also much more flexible in ATL/WTL, although you don't get automatic command routing for free (still one of MFC's best features, in my opinion). The downside is usually compilation time of course. Templates have their price...but I'm finding for most small to medium size projects (say up to about 100,000 lines) it's a price worth paying. Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
Anna-Jayne Metcalfe wrote:
The downside is usually compilation time of course. Templates have their price...but I'm finding for most small to medium size projects (say up to about 100,000 lines) it's a price worth paying.
Make sure you put all the template includes in stdafx.h (assuming you are using precompiled headers), and your compilation times shouldn't be so high. :) -- Pictures[^] from my Japan trip.
-
Anna-Jayne Metcalfe wrote:
The downside is usually compilation time of course. Templates have their price...but I'm finding for most small to medium size projects (say up to about 100,000 lines) it's a price worth paying.
Make sure you put all the template includes in stdafx.h (assuming you are using precompiled headers), and your compilation times shouldn't be so high. :) -- Pictures[^] from my Japan trip.
We do, but there's still a noticeable impact. Even if precompiled, #include files (which I've never been a fan of - I've always considered them archaic) have their price... Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
