Output console messages

[rreusser]

It might be nice to wrap console.log to return output messages instead of just returning the result only. As I recall, it's a little awkward since the way in which console interacts with arguments isn't fully covered by standards so it takes some care to do properly. Otherwise perhaps there's another way to intercept and forward these messages to the output.

[b3by]

I'm thinking, since log messages might be annoying sometimes, they could be triggered by a core command, like /printLogs, so that users can enable or disable it.

[rreusser]

I guess there are different possibilities:

• log all the time is maybe just annoying
• warn could be nice (like for "max depth exceeded" or similar)
• error may be similarly important

Of course could be fancy and roll them up over execution and give:

somemethod: you got a warning: ...
somemethod: you got a warning: ...
[150000 more warnings omitted]

in order to protect against offenders like me 😞

[b3by]

This really sounds like a nice idea. I'll wrap something up for the next package versione!

[rreusser]

I'm also imagining a notebook interface in which everything since the preceding > gets evaluated at the same time, but now I'm just getting into feature creep 😄

[b3by]

Eheheheh, that could also be funny, still, functions should be declared before being used, and this might be a pain. I was thinking about something like that in #6 but in that case, the evaluation would have been sequential.