Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » A problem with UPP application scale . . . UPP exonerated, the rest of the story.
Re: A problem with UPP application scale . . . UPP exonerated, the rest of the story [message #20203 is a reply to message #20202] Wed, 25 February 2009 01:44 Go to previous messageGo to previous message
Mindtraveller is currently offline  Mindtraveller
Messages: 916
Registered: August 2007
Location: Russia, Moscow rgn.
Experienced Contributor

In this case abstract classes (by the way, you may define pure virtual member with function body) are better than my solution. Because adding new member functions doesn`t cause full recompilation.
My proposal is (and was) about GUI elements only. If you, say, have Map<String,Ctrl> - then you may add GUI elements dynamically inside ctor. So adding any more GUI elements wouldn`t cause rebuild. But it looks rather artificial solution to me.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Compiler/Linker options
Next Topic: the debugger
Goto Forum:
  


Current Time: Wed Feb 19 09:10:17 CET 2020

Total time taken to generate the page: 0.00935 seconds