| View previous topic :: View next topic |
| Author |
Message |
jcesar
Joined: 26 Apr 2004
Posts: 5
|
 Posted: Thu May 27, 2004 2:34 pm Post subject: About the unicode/ansi aliases |
 |
|
In the current distribution of Core32, unicode / ansi aliases are isolated on a separate file wich is imported by the application programmer.
Converting commdlg.h I've found a couple of macros that used SendMessage and didn't had corresponding A/W versions so they sould use the same version that the programmer choose. For example:
| Code: |
#define CommDlg_OpenSave_GetFolderIDList(_hdlg, _pidl, _cbmax) \
(int)SNDMSG(_hdlg, CDM_GETFOLDERIDLIST, (WPARAM)_cbmax, (LPARAM)(LPVOID)_pidl)
|
Was converted to:
| Code: |
LRESULT CommDlg_OpenSave_GetFolderIDList(HWND _hdlg, LPVOID _pidl, UINT _cbmax)
{
return SendMessage(_hdlg, CommonDialogNotification.CDM_GETFOLDERIDLIST,
cast (WPARAM)_cbmax, cast (LPARAM)_pidl);
}
|
The problem is that the SendMessage alias isn't defined in my module but on unicode.d or ansi.d.
I don't know wich version should I use.
Thanks
_________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS$ d- s+:+ a-- C++> ULS++ P++ L+> !E W+++ N+ o? K? w++>
O---@ M V? PS+ PE Y+ PGP t+ 5- X+++@ R- tv+(++) b++> DI!
D++> G e+> h-- r- y+
------END GEEK CODE BLOCK------ |
|
| Back to top |
|
 |
jcesar
Joined: 26 Apr 2004
Posts: 5
|
| Posted: Tue Jun 01, 2004 4:02 pm Post subject: |
|
|
I have been thinking a little more on the topic and it seems we could just define the unicode/ansi aliases in the same file the functions are declared and still keep the unicode.d and ansi.d files (Wich are a really nice mecanism):
| Code: |
//unicode.d
version = UNICODE;
import winbase;
import winuser;
...
|
| Code: |
//ansi.d
version = ANSI; // Just don't define UNICODE
import winbase;
import winuser;
...
|
Then each file would be:
| Code: |
SendMessageW(...);
SendMessageA(...);
version (UNICODE)
{
alias SendMessageW SendMessage;
}
else
{
alias SendMessageA SendMessage;
}
|
What do you think?
_________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS$ d- s+:+ a-- C++> ULS++ P++ L+> !E W+++ N+ o? K? w++>
O---@ M V? PS+ PE Y+ PGP t+ 5- X+++@ R- tv+(++) b++> DI!
D++> G e+> h-- r- y+
------END GEEK CODE BLOCK------ |
|
| Back to top |
|
|
jcc7
Joined: 22 Feb 2004
Posts: 657
Location: Muskogee, OK, USA
|
| Posted: Tue Jun 01, 2004 7:22 pm Post subject: |
|
|
| jcesar wrote: | | I have been thinking a little more on the topic and it seems we could just define the unicode/ansi aliases in the same file the functions are declared and still keep the unicode.d and ansi.d files . . . |
How is this different than the way it's currently setup? Are you suggesting that the aliases in unicode.d/ascii.d be moved to other files? That sounds like a reasonable idea to me. I thought that was how the .h files were set up.
I think one of the most important goals is to keep the D port parallel (as much as possible) to the original header files. It would make correcting errors and updating to new headers that much easier. Also it would faciliate adding definitions from Y. Tomino's automatically-generated headers. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
