Lionel Ulmer <[EMAIL PROTECTED]> writes:
> The only problems I could see with this approach is that :
>
> - it cannot 'expect' more than one kind of error at the same time
I was thinking you could use a special value as a "wildcard" for the
error codes, in which case it wouldn't be tested for
> The main problem with that is that I don't think you can jump out of
> Xlib without corrupting its state. Also you'd need to properly unlock
> the tsx11 lock in case of exception, which will probably require an
> finally handler around each X call.
Well, seems you are right about X not liking t
Lionel Ulmer <[EMAIL PROTECTED]> writes:
> When discussing with Ove yesterday on #WineHQ about the handling of X
> errors, he told me about an idea of his : using exceptions to handle X
> errors.
The main problem with that is that I don't think you can jump out of
Xlib without corrupting its sta
Hi all,
When discussing with Ove yesterday on #WineHQ about the handling of X
errors, he told me about an idea of his : using exceptions to handle X
errors.
This way, when we have to explicitely handle X errors (as we will need to do
for XVidmode and XDGA2 due to some (stupidly done IMHO :-) ) s
