GetPrivateProfileString使用中的问题,(急)

flstx 2007-05-01 04:18:49
char buffer[255] , buffer2[255];

GetPrivateProfileString("UPDATE", "Version", "no value", buffer, 255, "C:\\x.ini");

CString version = buffer;

GetPrivateProfileString("RwxData", "RfwData", "no value", buffer2, 255, "C:\\x.ini");

CString version2 = buffer2;

--------------------Configuration: Rwx - Win32 Debug--------------------
Compiling...
RwxDlg.cpp
D:\Program Files\Microsoft Visual Studio\MyProjects\Rwx2\RwxDlg.cpp(364) : error C2110: cannot add two pointers
执行 cl.exe 时出错.

Rwx.exe - 1 error(s), 0 warning(s)

请问为什么出现这样的情况!!!?
...全文
831 6 打赏 收藏 转发到动态 举报
写回复
用AI写文章
6 条回复
切换为时间正序
请发表友善的回复…
发表回复
coldplay968 2008-03-18
  • 打赏
  • 举报
回复
jiefen
flstx 2007-05-01
  • 打赏
  • 举报
回复
是 GetPrivateProfileString(...);

你查查就知道为什么6参数了!
flstx 2007-05-01
  • 打赏
  • 举报
回复
= ="

问题我解决了

是我大意了,代码没错的.

谢谢各位!!!
yxz_lp 2007-05-01
  • 打赏
  • 举报
回复
你这个函数怎么又6个参数。
GetProfileString

The GetProfileString function retrieves the string associated with a key in the specified section of the Win.ini file.

Note This function is provided only for compatibility with 16-bit Windows-based applications, therefore this function should not be called from server code. Applications should store initialization information in the registry.


DWORD GetProfileString(
LPCTSTR lpAppName,
LPCTSTR lpKeyName,
LPCTSTR lpDefault,
LPTSTR lpReturnedString,
DWORD nSize
);

Parameters
lpAppName
[in] Pointer to a null-terminated string that specifies the name of the section containing the key. If this parameter is NULL, the function copies all section names in the file to the supplied buffer.
lpKeyName
[in] Pointer to a null-terminated string specifying the name of the key whose associated string is to be retrieved. If this parameter is NULL, the function copies all keys in the given section to the supplied buffer. Each string is followed by a null character, and the final string is followed by a second null character.
lpDefault
[in] Pointer to a null-terminated default string. If the lpKeyName key cannot be found in the initialization file, GetProfileString copies the default string to the lpReturnedString buffer. If this parameter is NULL, the default is an empty string, "".
Avoid specifying a default string with trailing blank characters. The function inserts a null character in the lpReturnedString buffer to strip any trailing blanks.

Windows Me/98/95: Although lpDefault is declared as a constant parameter, the system strips any trailing blanks by inserting a null character into the lpDefault string before copying it to the lpReturnedString buffer.
lpReturnedString
[out] Pointer to a buffer that receives the character string.
nSize
[in] Size of the buffer pointed to by the lpReturnedString parameter, in characters.
Return Values
The return value is the number of characters copied to the buffer, not including the null-terminating character.

If neither lpAppName nor lpKeyName is NULL and the supplied destination buffer is too small to hold the requested string, the string is truncated and followed by a null character, and the return value is equal to nSize minus one.

If either lpAppName or lpKeyName is NULL and the supplied destination buffer is too small to hold all the strings, the last string is truncated and followed by two null characters. In this case, the return value is equal to nSize minus two.

Remarks
If the string associated with the lpKeyName parameter is enclosed in single or double quotation marks, the marks are discarded when the GetProfileString function returns the string.

The GetProfileString function is not case-sensitive; the strings can contain a combination of uppercase and lowercase letters.

A section in the Win.ini file must have the following form:


[section]
key=string
.
.
.


An application can use the GetPrivateProfileString function to retrieve a string from a specified initialization file.

The lpDefault parameter must point to a valid string, even if the string is empty (that is, even if its first character is a null character).

Windows Server 2003 and Windows XP/2000/NT: Calls to profile functions may be mapped to the registry instead of to the initialization files. This mapping occurs when the initialization file and section are specified in the registry under the following keys:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\
CurrentVersion\IniFileMapping


When the operation has been mapped, the GetProfileString function retrieves information from the registry, not from the initialization file; the change in the storage location has no effect on the function's behavior.

The profile functions use the following steps to locate initialization information:

Look in the registry for the name of the initialization file under the IniFileMapping key.
Look for the section name specified by lpAppName. This will be a named value under the key that has the name of the initialization file, or a subkey with this name, or the name will not exist as either a value or subkey.
If the section name specified by lpAppName is a named value, then that value specifies where in the registry you will find the keys for the section.
If the section name specified by lpAppName is a subkey, then named values under that subkey specify where in the registry you will find the keys for the section. If the key you are looking for does not exist as a named value, then there will be an unnamed value (shown as <No Name>) that specifies the default location in the registry where you will find the key.
If the section name specified by lpAppName does not exist as a named value or as a subkey, then there will be an unnamed value (shown as <No Name>) that specifies the default location in the registry where you will find the keys for the section.
If there is no subkey or entry for the section name, then look for the actual initialization file on the disk and read its contents.

When looking at values in the registry that specify other registry locations, there are several prefixes that change the behavior of the .ini file mapping:


! - this character forces all writes to go both to the registry and to the .ini file on disk.
# - this character causes the registry value to be set to the value in the Windows 3.1 .ini file when a new user logs in for the first time after setup.
@ - this character prevents any reads from going to the .ini file on disk if the requested data is not found in the registry.
USR: - this prefix stands for HKEY_CURRENT_USER, and the text after the prefix is relative to that key.
SYS: - this prefix stands for HKEY_LOCAL_MACHINE\SOFTWARE, and the text after the prefix is relative to that key.

Requirements
Client Requires Windows XP, Windows 2000 Professional, Windows NT Workstation, Windows Me, Windows 98, or Windows 95.
Server Requires Windows Server 2003, Windows 2000 Server, or Windows NT Server.
Header Declared in Winbase.h; include Windows.h.

Library Link to Kernel32.lib.

DLL Requires Kernel32.dll.
Unicode Implemented as GetProfileStringW (Unicode) and GetProfileStringA (ANSI). Note that Unicode support on Windows Me/98/95 requires Microsoft Layer for Unicode.


See Also
Registry Functions, GetPrivateProfileString, WriteProfileString

--------------------------------------------------------------------------------

Last updated: March 2005 | What did you think of this topic? | Order a Platform SDK CD
© Microsoft Corporation. All rights reserved. Terms of use.



yxz_lp 2007-05-01
  • 打赏
  • 举报
回复
第一个字符串参数指的是程序名称
error C2110: cannot add two pointers
是不是这句错了GetPrivateProfileString("RwxData", "RfwData", "no value", buffer2, 255, "C:\\x.ini");
yxz_lp 2007-05-01
  • 打赏
  • 举报
回复
D:\Program Files\Microsoft Visual Studio\MyProjects\Rwx2\RwxDlg.cpp(364),364是哪一行。

16,471

社区成员

发帖
与我相关
我的任务
社区描述
VC/MFC相关问题讨论
社区管理员
  • 基础类社区
  • Web++
  • encoderlee
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告

        VC/MFC社区版块或许是CSDN最“古老”的版块了,记忆之中,与CSDN的年龄几乎差不多。随着时间的推移,MFC技术渐渐的偏离了开发主流,若干年之后的今天,当我们面对着微软的这个经典之笔,内心充满着敬意,那些曾经的记忆,可以说代表着二十年前曾经的辉煌……
        向经典致敬,或许是老一代程序员内心里面难以释怀的感受。互联网大行其道的今天,我们期待着MFC技术能够恢复其曾经的辉煌,或许这个期待会永远成为一种“梦想”,或许一切皆有可能……
        我们希望这个版块可以很好的适配Web时代,期待更好的互联网技术能够使得MFC技术框架得以重现活力,……

试试用AI创作助手写篇文章吧