User forums > Using Code::Blocks
Some C::B Suggestions...
thomas:
XCode does that, but it has a compiler espcially made for that purpose.
I think it would be quite hard and laggy, if one tried to implement it with plain normal gcc under Windows/Linux.
Shakes:
All valid points. But one has to point out, its already been done despite what seems impossible. If I'm not mistaken, the original Lint program was initially designed just for that purpose. Splint <http://splint.org/> <http://en.wikipedia.org/wiki/Splint_%28programming_tool%29> is a C code "interpretor" designed especially for checking code.
Even if this is not viable, the LaTeX plugin behaves intelligently around the problem, it simply gathers the info after each compile (which is done automatically at save) and then uses the output to display the (possible) errors in Lint form (so its not like double-click on error and it shows you where it is but rather underlines errors/warnings like Word). Note: LaTeX compilation is in general slower and has to be done multiple times to get references right in the document.
Anyway, hope that helps.
Cheers
takeshimiya:
--- Quote from: Shakes on November 16, 2006, 02:11:30 am ---All valid points. But one has to point out, its already been done despite what seems impossible.
--- End quote ---
There's always CINT, even trough it covers 95% of ANSI C and 85% of C++, it will be nice to have a plugin for it. :)
Shakes:
:o Thats even better lol
David Perfors:
--- Quote from: takeshi miya on November 16, 2006, 05:29:28 am ---
--- Quote from: Shakes on November 16, 2006, 02:11:30 am ---All valid points. But one has to point out, its already been done despite what seems impossible.
--- End quote ---
There's always CINT, even trough it covers 95% of ANSI C and 85% of C++, it will be nice to have a plugin for it. :)
--- End quote ---
There is one problem, it doesn't seems to work with MinGW :? Or I am doeing something wrong...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version