Redirect compiler warnings to file

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Redirect compiler warnings to file

Simon Denier-3
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Redirect compiler warnings to file

Nicolás Paez
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.

Saludos!
Nico.
blog: nicopaez.wordpress.com


On Sun, Sep 5, 2010 at 8:52 PM, Simon Denier <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Redirect compiler warnings to file

Simon Denier-3

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 <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev