User forums > General (but related to Code::Blocks)
BLITZ support?
thomas:
--- Quote from: Takeshi Miya on December 05, 2005, 05:52:15 pm ---Question: Do you think, at least in a distant future, that these features will be feasible in Code::Blocks?
--- End quote ---
Distributed builds or SMP builds will certainly be implemented, there is no doubt about this.
Predictive Compilation sounds like a nice thing, and it is certainly possible to be implemented. However, running compiles in the background while typing may be a major issue to notebook users or users who own little memory and slow CPUs. A compiler is not really conservative with resources, this has to be taken into account.
ZeroLink is technically certainly possible (at least under Windows I know how to do it, and very likely it is a lot easier under Linux), but this involves some OS-dependent stuff and a good amount of tampering which is not precisely portable.
Fix and Continue is a lot harder to implement. It is still possible of course, but it would involve a lot of things which are outright evil. I would not want it, even for all of its coolness.
takeshimiya:
--- Quote from: thomas on December 05, 2005, 11:49:51 pm ---Predictive Compilation sounds like a nice thing, and it is certainly possible to be implemented. However, running compiles in the background while typing may be a major issue to notebook users or users who own little memory and slow CPUs. A compiler is not really conservative with resources, this has to be taken into account.
--- End quote ---
Yes, from Apple User Guide: "On slower machines, enabling predictive compilation may interfere with Xcode performance during editing."
So, all the technologies remarked here are user-selectable of course.
Michael:
--- Quote from: Takeshi Miya on December 05, 2005, 08:43:31 pm ---I for myself would like to see C::B going mainstream so the entire world isn't just Java|.NET
--- End quote ---
Jave and .Net :?? Personally, I do not appreciate too much either Java or .NET. I sympathize much more for C++ :).
Michael
Ptomaine:
Sorry, I didn't explain what the BLITZ was.
First time, where I encountered the BLITZ approach was 'Ultimate++' IDE (http://upp.sourceforge.net).
Briefly speaking, BLITZ creates a single CPP file where several '#include' directives go with the source files and some '#define' directives. Thus the compiler executed ONLY ONCE for compilation but not for every source file.
So, here we go.
mandrav:
--- Quote from: Ptomaine on December 06, 2005, 11:39:46 am ---Briefly speaking, BLITZ creates a single CPP file where several '#include' directives go with the source files and some '#define' directives. Thus the compiler executed ONLY ONCE for compilation but not for every source file.
--- End quote ---
This can be done with every compiler, but I don't see the benefits in doing so. The tiniest change in a source file will need to compile all files again...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version