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++ Library support » U++ Core » Incorrect implementation of INITBLOCK (and similar macros) in case when flagBLITZ is not defined.
Re: Incorrect implementation of INITBLOCK (and similar macros) in case when flagBLITZ is not defined [message #31935 is a reply to message #31813] Fri, 08 April 2011 23:31 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13984
Registered: November 2005
Ultimate Member
kohait00 wrote on Tue, 29 March 2011 08:59


is this a general behaviour? can it be considered rule of thumb to rename the INITBLOCK containing cpp file to icpp file, if there is nothing in the file which will guarantee it's presence in linker later, like i.e. referenced code. if so, maybe this should be outlined somewhere in the docu



Well,

1) you have to aware about hits regardless INITBLOCK, because it affects all global initialization code (read: global constructors)

2) I can imagine situation where you want to put INITBLOCK into .cpp as well, with current behaviour
 
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: why not "T & Add(const T & x)" in all containers
Next Topic: ADDs: ValueMap
Goto Forum:
  


Current Time: Wed Jun 12 14:57:51 CEST 2024

Total time taken to generate the page: 0.03271 seconds