arielb1

These are compiler errors, not runtime errors. Reporting a traceback to the user is of course bad (through not as bad as some error messages).

New versions of g++ (4.9+) have much better error messages (g++ has better errors than gcc).

I still prefer just-HTML sites to the typical JS-based sites (e.g. the new Google Groups) I see.

In many contexts I would prefer a program to not try to recover (and possibly cause a mess) on unexpected input. Of course if you have a big process it may be a good idea to limit the scope of a failure to a smaller level.

You should first SHA-512 the password (to get a uniformly-64-byte string) and then apply bcrypt to that.

CompCert (compcert.inria.fr) kind-of gives C formal semantics.

Functional languages, along with Rust's linear type-system, can ensure this for single-ownership structures (trees, singly-linked lists), but not for structures with more complex ownership, like doubly-linked lists. The unpopular languages I was talking about were Agda and friends.