[Openmcl-devel] print leak will crash CCL/Windows/Cocotron app when WaltConsole is missing
ralex at cs.colorado.edu
Fri Dec 2 17:27:07 UTC 2011
In CCL GUI app (Coco/Cocotron), i.e., end-user applications, NOT developer tools, any call to print functions, or unwrapped errors, will make the (w)altConsole show up. This is super confusing to end-user and really of no help. Instructing them to type in values to continue are generally not appreciated. With errors wrapped up on the Mac we can just remove the AltConsole. Any leftover print leak will dump text into the Mac console which is OK. The same is not true for Cocotron Windows CCL apps. AFAIK removing the WaltConsole will instantly crash CCL if there is any print leak (accidental print perhaps due to errors). There is a not so widely known nor partially great Windows console that Cocotron does write to when using the NSLog function.
Is there any way to remove the WalConsole without running the risk of print leaks crashing the app? Acceptable solutions would be to just throw output away completely or to pipe it through NSLog. Ideally, just like on the Mac, this would be done by removing the WaltConsole app from the CCL windows bundle.
Prof. Alexander Repenning
University of Colorado
Computer Science Department
Boulder, CO 80309-430
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel