BOOL WINAPI IsWow64Process(

 __in HANDLE hProcess,

 __out PBOOL Wow64Process );

Parameters

hProcess

A handle to the process.

Wow64Process

A pointer to a value that is set to TRUE if the process is running under WOW64. Otherwise, the value is set to FALSE.

Return Value

If the function succeeds, the return value is a nonzero value.

If the function fails, the return value is zero. To get extended error information, call GetLastError.

Remarks

If the application is a 64-bit application running under 64-bit Windows, the Wow64Process parameter is set to FALSE.

To compile an application that uses this function, define _WIN32_WINNT as 0x0501 or later. For more information, see Using the SDK Headers.

#include <windows.h>
#include <stdio.h>

typedef BOOL (WINAPI *LPFN_ISWOW64PROCESS) (HANDLE, PBOOL);

LPFN_ISWOW64PROCESS fnIsWow64Process;

BOOL IsWow64()
{
    BOOL bIsWow64 = FALSE;

    fnIsWow64Process = (LPFN_ISWOW64PROCESS)GetProcAddress(
        GetModuleHandle(TEXT("kernel32")),"IsWow64Process");
  
    if (NULL != fnIsWow64Process)
    {
        if (!fnIsWow64Process(GetCurrentProcess(),&bIsWow64))
        {
            // handle error
        }
    }
    return bIsWow64;
}

void main()
{
    if(IsWow64())
        printf("Running on WOW64\n");
    else printf("Running on 32-bit Windows\n");
}

MSDN을 보면 아래와 같이 설명해놨다.

뭐...
경고 쯤이야 해도 상관 없지만~
이까이꺼  warning pragma로 해제해도 되겠지만~
보고 그냥 지나칠 수 없지!

상황은 대략 아래와 같다.

\include\cstdio(49) : warning C4995: 'gets': 이름이 #pragma deprecated로 표시되었습니다.
\include\cstdio(53) : warning C4995: 'sprintf': 이름이 #pragma deprecated로 표시되었습니다.
\include\cstdio(56) : warning C4995: 'vsprintf': 이름이 #pragma deprecated로 표시되었습니다.
\include\cstring(22) : warning C4995: 'strcat': 이름이 #pragma deprecated로 표시되었습니다.
\include\cstring(23) : warning C4995: 'strcpy': 이름이 #pragma deprecated로 표시되었습니다.
\include\cwchar(36) : warning C4995: 'swprintf': 이름이 #pragma deprecated로 표시되었습니다.
\include\cwchar(37) : warning C4995: 'vswprintf': 이름이 #pragma deprecated로 표시되었습니다.
\include\cwchar(39) : warning C4995: 'wcscat': 이름이 #pragma deprecated로 표시되었습니다.
\include\cwchar(41) : warning C4995: 'wcscpy': 이름이 #pragma deprecated로 표시되었습니다.

크아아아아아ㅇ니마어림나ㅓ리마너~
뭐냐 이거... ㅡ,.ㅡ

include 항목을 살펴보았다.

 [호출규약 : __cdecl]   <---ANSI C 함수호출규약 

[호출규약 : __stdcall] <---C++ 함수호출규약

[호출규약 : __fastcall]

The data types supported by Microsoft® Windows® are used to define function return values, function and message parameters, and structure members. They define the size and meaning of these elements.

The following table contains the following types: character, integer, Boolean, pointer, and handle. The character, integer, and Boolean types are common to most C compilers. Most of the pointer-type names begin with a prefix of P or LP. Handles refer to a resource that has been loaded into memory.

ASSERT

ASSERT( booleanExpression )

Parameters

booleanExpression

Specifies an expression (including pointer values) that evaluates to nonzero or 0.

Remarks

Evaluates its argument. If the result is 0, the macro prints a diagnostic message and aborts the program. If the condition is nonzero, it does nothing.

The diagnostic message has the form

assertion failed in file <name> in line <num>

where name is the name of the source file, and num is the line number of the assertion that failed in the source file.

In the Release version of MFC, ASSERT does not evaluate the expression and thus will not interrupt the program. If the expression must be evaluated regardless of environment, use the VERIFY macro in place of ASSERT.

Note   This function is available only in the Debug version of MFC.

Example

// example for ASSERTCAge* pcage = new CAge( 21 ); // CAge is derived from CObject.ASSERT( pcage!= NULL )ASSERT( pcage->IsKindOf( RUNTIME_CLASS( CAge ) ) )// Terminates program only if pcage is NOT a CAge*.

See Also   VERIFY

IMPLEMENT_DYNCREATE

IMPLEMENT_DYNCREATE( class_name, base_class_name )

Parameters

class_name

The actual name of the class (not enclosed in quotation marks).

base_class_name

The actual name of the base class (not enclosed in quotation marks).

Remarks

Use the IMPLEMENT_DYNCREATE macro with the DECLARE_DYNCREATE macro to enable objects of CObject-derived classes to be created dynamically at run time. The framework uses this ability to create new objects dynamically, for example, when it reads an object from disk during serialization. Add the IMPLEMENT_DYNCREATE macro in the class implementation file. For more information, seeCObject Class Topics in Visual C++ Programmer’s Guide.

If you use the DECLARE_DYNCREATE and IMPLEMENT_DYNCREATE macros, you can then use the RUNTIME_CLASS macro and the CObject::IsKindOf member function to determine the class of your objects at run time.

If DECLARE_DYNCREATE is included in the class declaration, then IMPLEMENT_DYNCREATE must be included in the class implementation.

Example

// CAge.hclass CAge : public CObject{     int num;public:     DECLARE_DYNCREATE(CAge)};//==============// CAge.cpp#include "stdafx.h"#include "CAge.h"IMPLEMENT_DYNCREATE(CAge, CObject) 

See Also   DECLARE_DYNCREATE, RUNTIME_CLASS, CObject::IsKindOf