On 03/09/2011 06:09 PM, eduardo fiss beloni wrote: > Here it is. The patch which makes xfreerdp end with the last thread's return > as the program exit code. Please comment.
It would be nice to have some documentation of what it was intended to do and what it should return in which situations. Are all these STANDARD_EXIT_CODEs used, or do they match some specification? EX_PROTOCOL doesn't sound descriptive for "failed to connect". It would be nice to have different exit codes for "failed to resolve name", "tcp connection rejected" and "premature close". Such exit codes that is "invented" by freerdp should be documented in the man page. In most cases you exit with the Set Error Info value? Isn't that 32 bits where at least 16 bits is used? exit() only returns 8 bit to the caller. How is that going to work? /Mads ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
