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 » How BLITZ works?
Re: How BLITZ works? [message #693 is a reply to message #692] Wed, 25 January 2006 20:21 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13980
Registered: November 2005
Ultimate Member
Well, by default, only .cpp files with include guards are qualified for blitz (this is easily checkable).

You can affect this using

#pragma BLITZ_APPROVE // to force the file to be BLITZed
#pragma BLITZ_PROHIBIT // to disallow

And you are correct about TheIDE going through the file, recording all #define(s) and placing conditional #undef(s) at the end of blitz file (#if(s) are ignored, that is why #undef(s) have to be conditional).

Actually, most of these actions are performed in header-dependency code and results are cached (per file timestamp).

I have planned to make Topic++ about BLITZ for quite a long time, but there is always something else to do.....

Respective code is in ide/Common/Hdepend.cpp and ide/Builders/CppBuilder.cpp.

BTW, BLITZ is by default active in debug mode only (where it has the most sense).
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Unix compilation fails
Next Topic: mingwm10.dll not needed?!
Goto Forum:
  


Current Time: Wed May 15 09:15:49 CEST 2024

Total time taken to generate the page: 0.03825 seconds