jakobkroeker

> we need to teach users how to program well ++ That is one of the core building blocks

``` --with-blas-libs=/usr/lib64/atlas/libsatlas.so.3 ``` worked for me ``` --with-blas-libs=-lopenblas ``` worked, too ``` --with-blas-libs=-lsatlas ``` did not... (ist is not in the search path): ``` ld -lsatlas --verbose ``` ``` attempt...

throwing something is not an error but a user might have been used a method incorrectly and he did not expect the exception and might want to figure out quickly...

No, I do not mean "error", I mean "throw ..."

It seems we have different ideas for "throw" concept in M2 My view/wish of 'exception' is an catcheable error distinguishable by error type and distinguishable from regular return value type....

> But exceptions are not like errors, and need not be brought to the attention of the user, by backtrace or otherwise. I guess I was not precise enought. *sigh*...

> I don't have a good recommendation. a first thought: what about opt-in collecting backtrace? (disabled by default)