Hi goran There are only two questions: 'Why when I load code do I have to open the transcript before to see the shadow and undeclared. and why I cannot click on an object and jump to the broken code?" Now with SimpleLogger I imagine that I cannot log compiler shadow, donât you :). 100 timesRepeat: [Goran repeatAfter: me what: âString sucks, string are dead objectsâ] Iâm coding in Smalltalk and not in perl! Now if you want to have syslog output this is probably one method definition in a new formatter in our nice frameworks. Do you have an output that shows what is needed for sysLog? because I can add a package for sysLog outputter. So we should have look at letting string habits outside of our nice house. Stef On 22 Feb 2014, at 15:51, Göran Krampe <goran@krampe.se> wrote:
Hey!
You didn't know about SimpleLog or?
http://map.squeak.org/packagebyname/simplelog
Not that it matters much, we can all use more logging tools ;) but... one "mistake" I think is that you don't match the standard syslog levels as described on the URL above.
SimpleLog even has a Morphic tool with it. Anyway, feel free to take whatever you like from it.
regards, Göran