C/C++ Programming Questions Not Worth Their Own Thread

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > C/C++ Programming Questions Not Worth Their Own Thread

Neslepaks: Sep 3, 2003

quote:

code:

char* buf = (char*)malloc(fileSize);

code:

str = (char *)calloc(strlen(visitIdent(_p_->u.stm_.ident_))+2, sizeof(char));

Don't do these casts when writing C. void pointers are always implicitly castable to other pointers, all you'll achieve is to hide warnings you'd want to see (like if you forgot to include the prototype for malloc, or there's a more serious type mismatch).

# ¿ Mar 5, 2008 00:23

Adbot: ADBOT LOVES YOU

# ¿ May 6, 2024 08:33

Neslepaks: Sep 3, 2003

ShinAli posted:

Not a C question really but I wanna know how to set up vim to be a pretty good IDE for C programming.

I saw a website out there describing out to set up vim for python, and had all these neat things like a debugger, code completion, COLOR, and so forth. I'm starting to like vim (even though I don't have a handle on all the commands and stuff yet), and since I'm going to be using vim for the entire semester, I'd like to configure it a bit for C.

You guys got anything?

These are my C specific settings:

autocmd BufRead,BufNewFile *.c,*.h,*.cc,*.cxx,*.hxx set cindent formatoptions=corq cinoptions=:0(0 textwidth=72 sm comments=sr:/*,rmb:*,exr:*/

That does auto-indentation with lining up the way I like it, paren/brace/bracket-matching, automatic comment formatting and wrapping (ie, you write /*<enter>, it fills in " * " for you, etc). Colors is just :syntax on.

I don't use make integration and that stuff much, but see :help make.

# ¿ Sep 9, 2008 13:38

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > C/C++ Programming Questions Not Worth Their Own Thread