This looks good :)

One thing to take into account is that there is already a 'log' syntax in the engine module which Ben et al. have been using. I don't think it conflicts but would be good to think about how we can roll them into one.

Yes, I'd really like to unify the syntaxes. The problem is that the engine lib's log syntax supports format strings and I'm not quite ready to implement a formatting engine in LCB.

Well the engine log command was a 'quick and dirty' thing so Ben et al could debug their code... It should perhaps be ear-marked as temporary :)

Logging should really be the domain of the standard library level I think - as long as the engine can connect up to the output of the lower level logging facilities to display them in the IDE.

Well, one option would be to provide a way to register a "log dispatcher" function callback with libsystem. I wish it was feasible to do engine bits in pure LCB. 😉

For our server code we've got a log handler, which just prefixes each line with a timestamp and an indent. The indent can be incremented or decremented which can be useful to give some indication of where messages come from in the call stack.

@livecodestephen For server stacks, we really should provide a way to use syslog(3), which will take care of all the PID / timestamp / etc. information, log storage, log rotation, etc.