[Swift-devel] [Swift-commit] r3835 -trunk/src/org/griphyn/vdl/karajan/functions (fwd)

[Justin M Wozniak]

I would actually prefer that the default Swift output, even in error 
cases, not contain Java stack details.

On Mon, 3 Jan 2011, jon.monette at gmail.com wrote:

> I agree with Mihael. The full java stack trace for the error should be 
> in the log and Swift should just report the Swift error during the 
> execution. 
>
> -----Original Message-----
> From: Mihael Hategan <hategan at mcs.anl.gov>
> Sender: swift-devel-bounces at ci.uchicago.edu
> Date: Mon, 03 Jan 2011 13:30:31
> To: Justin M Wozniak<wozniak at mcs.anl.gov>
> Cc: <swift-devel at ci.uchicago.edu>
> Subject: Re: [Swift-devel] [Swift-commit] r3835 -
> 	trunk/src/org/griphyn/vdl/karajan/functions (fwd)
>
> If the full trace was logged to the... log then it should please both
> sides.
>
> Mihael
>
> On Mon, 2011-01-03 at 09:43 -0600, Justin M Wozniak wrote:
>> This looks right for end users, but for development it really helps to get
>> a full stack trace.  Is it possible to turn on the full trace with a
>> runtime option?
>>  	Justin
>>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>

-- 
Justin M Wozniak