81–90 of 97 posts
Earlier quoted context omitted.
I usually try to fix as many errors as I can identify before recompiling. And yes, I usually fix from the bottom up, because that way my changes don't alter the line numbers of future fixes. On large projects, recompile time can be significant.
I think you need to upgrade you editor. For instance both vim & emacs are smart enough to adjust for inserts and removals.
Earlier quoted context omitted.
I usually try to fix as many errors as I can identify before recompiling. And yes, I usually fix from the bottom up, because that way my changes don't alter the line numbers of future fixes. On large projects, recompile time can be significant.
Yes, sure, large projects can take time to compile, but doesn't your compile environment just try to recompile the last file that it failed on during the build? That is, if in trying to build my app FooBar, and foo.c compiles ok but bar.c fails, when I try to run the build the next time having modified bar.c, it starts by trying to compile bar.c anyway... So I guess what I'm trying to say is that I don't understand t…
Wow, the clang error messages are really good. I've never seen a compiler produce such user-friendly error messages.
According to the clang home page as of March 7th 2010, "Clang's C++ support is currently alpha quality at best, but is evolving rapidly." Obviously, clang does not mean to attract C++ developers. For a while, I'd been adamant about developing in C and not C++. One day I discovered that I'd hand-coded a vtable in order to allow polymorphism in structures of function pointers. The next day, I halved the project complex…
I've found myself in a similar situation. I am writing embedded software which needs to be as portable as possible, but I've found myself starting to implement polymorphism and objects in C. I am tempted to ignore platforms that lack a C compiler and switch to C++, but the reduced predictability of runtimes has kept me from doing so thus far.
Earlier quoted context omitted.
I think you need to upgrade you editor. For instance both vim & emacs are smart enough to adjust for inserts and removals.
I use vim. How do I get it to adjust for edits?
Earlier quoted context omitted.
yeah, I'm thinking this might be more useful for c++ :)
In the meantime before clang fully supports C++ I would appreciate a flag for GCC that just gives me abbreviated error info: file.cpp:65: error: please have a look at this line and see if anything jumps out at you. as that is basically all GCC C++ errors are good for.
g++ [options] | sed -e 's/^(.*: (error|warning):).*/\1 please have a look at this line and see if anything jumps out at you/'I've had 40% speed-ups on some math-heavy C code simply by switching from gcc to clang.
Which version of gcc? I had a 2x speedup a few years ago on math-heavy code (FFTs) by switching from gcc 4.2 to gcc 3.4 -- apparently there was a known issue in gcc's optimizer where it would flag too many values as "keep this in a register" and end up spending lots of time moving data to and from the "register overflow space" on the stack. (I don't know if this has been fixed -- as I said, it was a few years ago tha…
Since when is it hard to find and correct syntax errors that are preventing your C code from compiling?
I can think of one example, heavy use of macros can create a syntax error nightmare. One of the projects I've worked on (I had inherited it without documentation) had some seriously obtuse nested macros that threw a spanner in the works at least once.
-E Stop after the preprocessing stage; do not run the compiler proper.
The output is in the form of preprocessed source code, which is
sent to the standard output.
Input files which don't require preprocessing are ignored.
Earlier quoted context omitted.
One point was mentioned - recompiling time may be huge. On the other hand - if the recompile time is tiny, I don't bother with any specific order, I just fix what I see as trivial first. But when you see the clang's very verbose errors - how many can you fit on the screen? 10? 15? To make sure none of the last ones depend on some code guessing, you'd have to scroll to the top every time, instead of just fixing what y…
How long is recompiling really going to be if it's one file, though? I'm not talking about C++, which clang isn't quite fluent in yet, but one file of pure C shouldn't take long to compile. Or have I not been compiling the right C files?
I've been bitten by the dependencies in C++ before. I have this file "image.h" which contains a templated image class with quite a few algorithms. My app is about image processing, so nearly everything uses the image datatype. I hate having to edit this file because it means recompiling nearly everything. Of course templates make it much worse than pure C...
Earlier quoted context omitted.
I think you need to upgrade you editor. For instance both vim & emacs are smart enough to adjust for inserts and removals.
I use vim. How do I get it to adjust for edits?
As for turning it on or off, I've never had too, unless it's part of cindent.