You can set the NonInteractiveTranscript to be used when compiling and then set it back to the ThreadSafeTranscript when done.
Will not play nice with other concurrent users of Transcript so make this in an atomic operation... Will allow you to catch the errors there. There was a thread about having more than one transcript so maybe you can have your own for this. Is Pharo6 supporting that already? Isn't the CodeImporter having what you need when doing a fileIn;? (Ok that means chunk format text but seems ok to me). Phil Le 14 mars 2017 19:16, "stepharong" <stephar...@free.fr> a écrit : > Marcus will certainly reply. > We are going towards a fluid interface for compiler because all the > messages with multiple arguments > do not work well for composition. > > Hi, >> >> I'm wondering how to programmatically compile a method. I tried using a >> variant of >> ClassDescription>>compile:*:notifying: >> However, on a method with undeclared variables, when the Transcript is >> open there seems to be no way to avoid a message being written there. >> Further, the requestor passed as a notifier in the above method is not even >> notified when the compilation context is not interactive. >> >> What is the correct way to use the compiler programmatically and in a non >> interactive batch, still being able to catch all the compilation errors and >> warnings? >> > > We should do another pass on the way erors are reported and it should not > be just writing in the transcript. > > >> Thanks >> Raffaello >> >> > > -- > Using Opera's mail client: http://www.opera.com/mail/ > > >
