History question: Oringins of "Afx" 
Author Message
 History question: Oringins of "Afx"

Here's a history question for all the longtime MFC user's. How did the
widespread use of the "Afx" prefix in MFC come about? Is it an acronym?

Many thanks.

--
To reply via e-mail, delete NOSPAM from the reply address.



Mon, 09 Sep 2002 03:00:00 GMT  
 History question: Oringins of "Afx"
I've always wondered that myself!


Mon, 09 Sep 2002 03:00:00 GMT  
 History question: Oringins of "Afx"

Quote:

>Here's a history question for all the longtime MFC user's. How did the
>widespread use of the "Afx" prefix in MFC come about? Is it an acronym?

Yes; it stands for Application Frameworks. Why the X?

Probably because X is a cool letter (Like ActiveX, X-Windows,
X-Men, X-Fighter, ad infinitum).

The Application Frameworks project was MS's first attempt
to make a class library for windows. The team produced a
beautiful, well-crafted, textbook perfect class library for
Windows.

It also ran as fast as a one-legged dog. By using textbook
perfect class design, they re-implemented  a ton of things
that Windows does internally, and they did so in a general,
non-optimized fashion, where Windows is internally
performance optimized.

It might have been better on modern machines; in those
days, the additional overhead was just too much, and
this killed Application Frameworks. MS replaced
this project with MFC. MFC took the reverse approach,
building the library bottom-up instead of top-down (this
is one of the reasons MFC has so many warts).

However, the Application Frameworks team had coded
a large number of functions and macros that were very
valuable; they all were prefixed AFX_ of Afx, and were
incorporated into MFC.



Mon, 09 Sep 2002 03:00:00 GMT  
 History question: Oringins of "Afx"
Many thanks for the info., Ron.

Regards.



Quote:


> >Here's a history question for all the longtime MFC user's. How did the
> >widespread use of the "Afx" prefix in MFC come about? Is it an acronym?

> Yes; it stands for Application Frameworks. Why the X?

> Probably because X is a cool letter (Like ActiveX, X-Windows,
> X-Men, X-Fighter, ad infinitum).

> The Application Frameworks project was MS's first attempt
> to make a class library for windows. The team produced a
> beautiful, well-crafted, textbook perfect class library for
> Windows.

> It also ran as fast as a one-legged dog. By using textbook
> perfect class design, they re-implemented  a ton of things
> that Windows does internally, and they did so in a general,
> non-optimized fashion, where Windows is internally
> performance optimized.

> It might have been better on modern machines; in those
> days, the additional overhead was just too much, and
> this killed Application Frameworks. MS replaced
> this project with MFC. MFC took the reverse approach,
> building the library bottom-up instead of top-down (this
> is one of the reasons MFC has so many warts).

> However, the Application Frameworks team had coded
> a large number of functions and macros that were very
> valuable; they all were prefixed AFX_ of Afx, and were
> incorporated into MFC.



Mon, 09 Sep 2002 03:00:00 GMT  
 History question: Oringins of "Afx"
Many thanks, Ron!



Quote:


> >Here's a history question for all the longtime MFC user's. How did the
> >widespread use of the "Afx" prefix in MFC come about? Is it an acronym?

> Yes; it stands for Application Frameworks. Why the X?

> Probably because X is a cool letter (Like ActiveX, X-Windows,
> X-Men, X-Fighter, ad infinitum).

> The Application Frameworks project was MS's first attempt
> to make a class library for windows. The team produced a
> beautiful, well-crafted, textbook perfect class library for
> Windows.

> It also ran as fast as a one-legged dog. By using textbook
> perfect class design, they re-implemented  a ton of things
> that Windows does internally, and they did so in a general,
> non-optimized fashion, where Windows is internally
> performance optimized.

> It might have been better on modern machines; in those
> days, the additional overhead was just too much, and
> this killed Application Frameworks. MS replaced
> this project with MFC. MFC took the reverse approach,
> building the library bottom-up instead of top-down (this
> is one of the reasons MFC has so many warts).

> However, the Application Frameworks team had coded
> a large number of functions and macros that were very
> valuable; they all were prefixed AFX_ of Afx, and were
> incorporated into MFC.



Fri, 18 Oct 2002 03:00:00 GMT  
 
 [ 5 post ] 

 Relevant Pages 

1. Disabling "History" in the IE

2. "Results History" in VC6

3. Using "history" of EditBox contents

4. remove() vrs fopen("""w")

5. Displaying binary data as ascii "1"'s and "0"'s

6. Looking for "Shroud"/"Obfus"

7. ""help with TSR""

8. Parse trees and "("")"

9. Error "free"-ing "malloc"-ed memory

10. Displaying binary data as ascii "1"'s and "0"'s

11. Attention "C"/"C++" gurus and "C" newbees

12. merits of "#define", "const", and "enum" ???

 

 
Powered by phpBB® Forum Software