On 11/15/10 00:11, Joost 't Hart wrote: Hi!
>> 3. Capture the output from stderr also. Stockfish writes to stderr on >> an error exit, but the message vanishes because there is no console >> window. > > Hm, I like what you say but this could mean quite some work, as Scid is > used to parse the stuff coming from the engine. So we would need to add > the notion that something that cannot be understood should be sent in > raw format to the engine window? I'd be pretty careful here and crosscheck what UCI definition says about stderr. AFAIK it is not used and therefore one can't expect anything decent on that channel. In other words: we would not want to handle very other engine separately cause the programmer doesn't follow the standards. More likely than parsing this and that unstructured output I'd raise a bug report @ stockfish. ;) > As to the implementation: Currently we open the engine's standard output > as "| <engine binary>" > Should this be replaced by something like "| <engine binary> 2&>1"? > I am not the expert in this respect, but I guess that this might not > work in windows...? Isn't this even shell specific? I know the above to works in bash but being a long year tcsh user (yes, some BSD in the past crossed my way heavily) I know that I resorted to call sh for some specifics like that resulting in me to convert to zsh in the end. Now it could be that the above is some tcl construction, than it might be portable still the above applies, IMHO. cu Alexander ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
