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 » Developing U++ » U++ Developers corner » Possible solution of "icpp problem"
Re: Possible solution of "icpp problem" [message #46851 is a reply to message #46850] Sun, 28 August 2016 10:07 Go to previous messageGo to previous message
Mindtraveller is currently offline  Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.
Experienced Contributor

First of all, let's think do we really need to keep icpp-compatibility at all. Or it is possible to forget about them once and for all.

Talking about the solution proposed (to inject registration calls with header - if I understand it correctly), I think this is possible way, but it has one [possible] issue with initialization order. We can't predict the way headers are included and we can't predict the sequence of initialization.
I always wondered why plugins are not initialized inside CONSOLE_APP_MAIN/GUI_APP_MAIN or with auto-initialization classes. (I mean something like that: http://zeuxcg.org/2010/10/10/death-by-static-initialization/ )

[Updated on: Sun, 28 August 2016 10:12]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [Solved] Instant Upp crash on char input
Next Topic: Parser error: Unterminated string
Goto Forum:
  


Current Time: Mon Apr 29 15:56:34 CEST 2024

Total time taken to generate the page: 0.03292 seconds