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.
Incorrect implementation of INITBLOCK (and similar macros) in case when flagBLITZ is not defined. [message #16423] Fri, 13 June 2008 21:33 Go to previous message
Novo is currently offline  Novo
Messages: 1371
Registered: December 2006
Ultimate Contributor
In such situation MK__s is defined as:

#define MK__s MK__s_(__LINE__)

And that means that INITBLOCK must always be put on lines with different line numbers (not just in one file, but in all files).
Otherwise INITBLOCK will produce functions having the same name, and as a result duplicate symbol names.

This issue prevents me from compiling of U++ using MSVC project files. (Have no idea how TheIDE does that.)

I’ve tried to improve INITBLOCK using __COUNTER__ macro, but couldn’t succeed in that.



Regards,
Novo

[Updated on: Fri, 13 June 2008 22:13]

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
Previous Topic: why not "T & Add(const T & x)" in all containers
Next Topic: ADDs: ValueMap
Goto Forum:
  


Current Time: Fri Nov 01 01:01:38 CET 2024

Total time taken to generate the page: 0.03097 seconds