[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/5] win32: Use ANSI functions
From: |
Bruno Haible |
Subject: |
Re: [PATCH 1/5] win32: Use ANSI functions |
Date: |
Fri, 2 Oct 2009 13:06:28 +0200 |
User-agent: |
KMail/1.9.9 |
I wrote:
> It would be best if clisp would change its macro 'UNICODE' to
> 'ENABLE_UNICODE'.
This is done now.
Paolo Bonzini wrote:
> > 1) Ability to look up the documentation. The next developers to maintain
> > this code should be able to google the function names and use the
> > names that are commonly in use.
>
> While I'll drop this patch, I'll note that we _do_ use *A names when we
> get functions from DLLs. So in some sense I was adding consistency...
In some weird sense, yes :-) But really, this *A suffix is so much of a
plague that it's better to limit it to the GetProcAddress arguments.
Bruno
- Re: [PATCH 4/5] Handle Windows CE and rewrite NT version handling., (continued)
- Re: [PATCH 2/5] uname: use only one OSVERSIONINFOEXA struct, use ANSI version, Bruno Haible, 2009/10/01
- Re: [PATCH 2/5] uname: use only one OSVERSIONINFOEXA struct, use ANSI version, Bruno Haible, 2009/10/01
- Re: [PATCH 2/5] uname: use only one OSVERSIONINFOEXA struct, use ANSI version, Paolo Bonzini, 2009/10/01
Re: [PATCH 1/5] win32: Use ANSI functions, Jim Meyering, 2009/10/01
Re: [PATCH 1/5] win32: Use ANSI functions, Bruno Haible, 2009/10/01