Re: Win32 signal code - first try

From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: 'Magnus Hagander ' <mha(at)sollentuna(dot)net>, "'pgsql-patches(at)postgresql(dot)org '" <pgsql-patches(at)postgresql(dot)org>
Cc: 'pgsql-hackers-win32 ' <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: Win32 signal code - first try
Date: 2004-01-09 00:18:37
Message-ID: A02DEC4D1073D611BAE8525405FCCE2B0280CB@harris.memetrics.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32 pgsql-patches


> Also, do we want this one #ifdef:ed in every place, or just
> #define it to nothing at all on non-windows platforms?

I imagine the latter will be cleaner.

> Anyway. Comments on these points in particular, and in the whole thing in
general? Workable path?

I think it looks great. Well done!

Cheers,
Claudio
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Tom Lane 2004-01-09 00:24:04 Re: fork/exec patch: pre-CreateProcess finalization
Previous Message Claudio Natoli 2004-01-09 00:14:18 Re: Signals on Win32 (yet again)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-01-09 00:24:04 Re: fork/exec patch: pre-CreateProcess finalization
Previous Message Tom Lane 2004-01-08 23:41:15 Re: Patch of intarray module in v7.4.1