Tag Info

1

This is not an answer, merely some observations I've made in the past. data1 = Reap[TraceScan[Sow, 1/0, TraceInternal -> True]][[-1, 1]]; Length[data1] (* 182126 *) data2 = Reap[TraceScan[Sow, Quiet[1/0], TraceInternal -> True]][[-1, 1]]; Length[data2] (* 39 *) So we see about 4670 times many function calls are made when a message is generated. I ...

3

Assuming you mean this window: If all goes well, no messages to the console or the notebook will be issued. You can with @Szabolcs Note control where error messages are printed. Either to the console or to the notebook. My advice here: let's keep the default settings. According to Documentation Center: If something goes very wrong with a calculation ...

2

The question is not completely clear to me but do take a look at your message printing settings in Mathematica's preferences: By default, kernel messages go to the notebook where the evaluation triggering them happened, not the messages window.

2

Clearing Attributes and looking at the definition of the FinancialData reveals that it is just a stub that loads the corresponding paclet on the first evaluation: ClearAttributes[FinancialData, {Protected, ReadProtected}] FullDefinition@FinancialData FinancialData := SystemDumpAutoLoad[Hold[FinancialData], Hold[\$FinancialDataSource, ...

1

The following works pretty well, at least in Mathematica 10: On the menu bar, go to Evaluation/Debugger Controls/Show Debugger Tools Window. On the window that pops up, check the box to "Break at Messages" It will then stop and display a green box around the code that is outputting an error message.

Top 50 recent answers are included