Re: [Pharo-project] [Moose-dev] Re: Redirect compiler warnings to file
probably note. And this si not surprising a ssystem without systematic engineering over 10 years cannot compete with one that got it. We will fix that but this will take some time and effort Stef On Sep 7, 2010, at 11:20 AM, TimM wrote: > Philippe Marschall wrote: > >> And an easy way to redirect to sdtout or stderr would help for things >> like Hudson. > > I found that in Dolphin when I was running with Cruise Control, that I > installed a subclassed Transcript that logged both to the screen and to a > file. > > I wonder if that might be an easy fix for Pharo? > > Tim > > > ___ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [Moose-dev] Re: Redirect compiler warnings to file
Philippe Marschall wrote: And an easy way to redirect to sdtout or stderr would help for things like Hudson. I found that in Dolphin when I was running with Cruise Control, that I installed a subclassed Transcript that logged both to the screen and to a file. I wonder if that might be an easy fix for Pharo? Tim ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [Moose-dev] Re: Redirect compiler warnings to file
Yes! Stef On Sep 5, 2010, at 10:46 PM, Philippe Marschall wrote: > On 05.09.2010 21:26, Stéphane Ducasse wrote: >> I hope that Opal will pay attention to such a point. > > And an easy way to redirect to sdtout or stderr would help for things > like Hudson. > > Cheers > Philippe > > > ___ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [Moose-dev] Re: Redirect compiler warnings to file
On 05.09.2010 21:26, Stéphane Ducasse wrote: > I hope that Opal will pay attention to such a point. And an easy way to redirect to sdtout or stderr would help for things like Hudson. Cheers Philippe ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [Moose-dev] Re: Redirect compiler warnings to file
I hope that Opal will pay attention to such a point. Stef >> Indeed, that's one way it works. It seems like Encoder typically generates >> this kind of message (Undeclared and shadowed variable) in a few places. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [Moose-dev] Re: Redirect compiler warnings to file
On 5 sept. 2010, at 20:55, Nicolás Paez wrote: > Up to what I saw, the class the writes to the Transcript is : > UndeclaredVariableWarning>>defaultAction. > But it is possible some other classes do the same. Indeed, that's one way it works. It seems like Encoder typically generates this kind of message (Undeclared and shadowed variable) in a few places. > > Saludos! > Nico. > blog: nicopaez.wordpress.com > > > On Sun, Sep 5, 2010 at 8:52 PM, Simon Denier wrote: > Hi > > When loading large chunks of code (like Moose), some warnings appear in the > Transcript. The problem is the Transcript has a limited size and that with > all information dumped into, the first one get lost before we can take a look > at them. > > Does anyone know a way to capture/redirect the Transcript output to a file, > or the output from Compiler (maybe using the requestor parameter?) > > -- > Simon > > > > > ___ > Moose-dev mailing list > moose-...@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > ___ > Moose-dev mailing list > moose-...@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
