From: | Katie Ward <kward(at)peerdirect(dot)com> |
---|---|
To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Win32 Technical Questions |
Date: | 2003-02-03 17:54:10 |
Message-ID: | JGEBJABBEAPBBHICKILIAEBLCFAA.kward@peerdirect.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The only MFC dependency is CWinApp, which I agree can be replaced. The rest
of it is written in c++ -- no MFC dependencies. C++ is still important
because of the critical-scection locking/unlocking through automatic stack
variables.
Katie
> -----Original Message-----
> From: Merlin Moncure [mailto:merlin(dot)moncure(at)rcsonline(dot)com]
> Sent: Monday, February 03, 2003 11:51 AM
> To: Katie Ward
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Win32 Technical Questions
>
>
> >Can the ConsoleApp thing be written in C so we don't have to get an
> >extra C++ compiler for one file (for those who don't want to use the
> >Microsoft toolchain)?
>
> Critical sections and semaphores and mutexes are all available from the
> win32 API. I agree with Peter: I am not sure it is a good idea to
> introduce MFC dependency for process control and application
> initializations. This would allow compilation without having the MFC
> (although, Borland supplies a version of the MFC with its non-free
> compilers). Also, a C++ compiler would not be required although this to
> me as strictly an aesthetic point.
>
> Likewise, I think the API functions are the best choice for file i/o for
> possible adaption of asynch file i/o.
>
> Despite the name, the apps written carefully using the win32 api should
> generally compile ok in 64 bit environment.
>
> Merlin
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Copeland | 2003-02-03 18:24:14 | Re: PGP signing releases |
Previous Message | wade | 2003-02-03 17:32:20 | Re: POSIX regex performance bug in 7.3 Vs. 7.2 |