hlp its urgent
-
Static/compile time polymorphism has another form also, which is extensively used by ATL classes. http://en.wikipedia.org/wiki/Curiously_recurring_template_pattern[^]
Yes, that's one of the reasons you never need a code obfuscator for
ATLsources...If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Yes, that's one of the reasons you never need a code obfuscator for
ATLsources...If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]Nice joke :)
-
There you have it. :) Let's leave it to him to choose what he wants.
«_Superman_» I love work. It gives me something to do between weekends.
Microsoft MVP (Visual C++) -
sir i want to know that if i write two function with same name(Polymorphism function overloading) then both function will take same memory or different.. if both will take same memory then how???
They will actually become 2 different functions with different names. The change in names is done by the compiler and this is called name mangling.
«_Superman_» I love work. It gives me something to do between weekends.
Microsoft MVP (Visual C++) -
They will actually become 2 different functions with different names. The change in names is done by the compiler and this is called name mangling.
«_Superman_» I love work. It gives me something to do between weekends.
Microsoft MVP (Visual C++) -
sir i want to know that if i write two function with same name(Polymorphism function overloading) then both function will take same memory or different.. if both will take same memory then how???
DX Roster wrote:
Polymorphism function overloading
Did you follow our discution ? If yes, do you understand the difference between function overloading (two functions with the same name but different arguments) and function overriding (a function which is redefined in a child class) ? So please, indicates which is the exact case you are interested in, because these are two completely different cases.
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++ -
They will actually become 2 different functions with different names. The change in names is done by the compiler and this is called name mangling.
«_Superman_» I love work. It gives me something to do between weekends.
Microsoft MVP (Visual C++)In case of overloading yes. It still isn't clear (at least for me) if he really meant overloading (he didn't answer the question, just put the words in a different order ;P ).
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++ -
Anyway, if you meant overloading or overriding, both functions will start at different memory addresses (two different functions cannot start at the same memory address, it doesn't make sense).
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++ -
Nice joke :)
-
When you overload a function, basically you're giving the same name to two different functions (the compiler produces two functions with two different names in the object file) hence two different portions of code memory are, of course, used. :)
DX Roster wrote:
Please reply me as earlier as possible
:-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]This is known as Name Mangling[^]. Regards, Paresh.
-
This is known as Name Mangling[^]. Regards, Paresh.
Yes, I know that. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]