🔒 Locked

WTF?

Started by Etnu Jul 5, 2004 at 4:09 AM 5 replies 650+ views

Original Post

108

Jul 5, 2004 at 4:09 AM


HRESULT WINAPI
    D3DXCompileShaderFromFileW(
        LPCWSTR                         pSrcFile,
        CONST D3DXMACRO*                pDefines,
        LPD3DXINCLUDE                   pInclude,
        LPCSTR                          pFunctionName,
        LPCSTR                          pProfile,
        DWORD                           Flags,
        LPD3DXBUFFER*                   ppShader,
        LPD3DXBUFFER*                   ppErrorMsgs,
        LPD3DXCONSTANTTABLE*            ppConstantTable);

Why on earth would you do that? The W is supposed to mean "hey, everything here uses wide characters", not "some things might use wide characters...others will use ordinary characters!" *smack*

xyzzy00

Jul 5, 2004 at 5:29 AM

Its because the shader code, entrypoint name, and profile name, are only allowed to be ascii. Not much point for the function to take everything in unicode, if it will just convert it back.

xyzzy

Muhammad Haggag

156

Muhammad Haggag

Jul 5, 2004 at 5:57 AM

Just a minor comment: You're a really senior member Etnu. So you should've created the topic with a meaningful title (like D3DXCompilerShaderFromFileW oddness)

IFooBar

119

IFooBar

Jul 5, 2004 at 9:13 AM

Must be one of those ->[totally]<- days.

Etnu

Author

108

Etnu

Jul 5, 2004 at 9:19 AM

Actually, it was a late night spent trying to figure out why after altering my shader loaders to work with multiple versions it stopped compiling.

I came up with a work around, but the whole thing just seemd kind of counter-intuitive. Sorry about the title.

Pipo DeClown

156

Pipo DeClown

Jul 5, 2004 at 12:08 PM

WTF?

SiCrane

Mod

473

SiCrane

Jul 5, 2004 at 9:24 PM

Quote:
Original post by Etnu
Why on earth would you do that? The W is supposed to mean "hey, everything here uses wide characters", not "some things might use wide characters...others will use ordinary characters!"

*smack*

Actually it means all the strings designated as T strings in the non A/W declaration will be treated as wide character strings. There are actually quite a few areas in Windows programming where even when using wide character versions of functions you need narrow strings. The original rich edit control comes to mind immediately.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.