[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150512140613.GA19462@openwall.com>
Date: Tue, 12 May 2015 17:06:13 +0300
From: Aleksey Cherepanov <lyosha@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [core john] [Johnny] Windows event loop
Shinnok,
On Tue, May 12, 2015 at 04:25:47PM +0300, Shinnok wrote:
> As you probably have figured out by now, this took me a considerable
> amount of time to do, so Mathieu, next time around, please strive a
> bit more when I tell you that you haven't been exhaustive enough
> regarding an approach.
Wow!
I guess it would be enough on your side to prove that ctrl-c works for
just 1 build and leave the rest of the work to Mathieu.
> Aleksey, you have your answer in this e-mail. I hope it's obvious enough.
This solution looks really great for those builds that work with it. I
doubt that the helper program may be helpful for other builds (though
there is a difference between ctrl-c and ctrl-break: ctrl-break is
always the signal, so anything may be possible).
Though my question was about WM_CLOSE exactly. Is WM_CLOSE still
needed?
Thanks!
--
Regards,
Aleksey Cherepanov
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
