1

Topic: Whether is generally available DLL with strsafe-functions?

The dial-up of strsafe-functions (StringCbXxx/StringCchXxx) has been announced in SDK for XP SP2 (2004 year). However, even in last SDK/WDK all of them are connected from static library, instead of imported from DLL. MS and did not find time to suppose them in generally available DLL how lstrXxx and w [v] sprintf, or I that do not understand?

2

Re: Whether is generally available DLL with strsafe-functions?

Hello, Evgenie Muzychenko, you wrote: I eat> However, even in last SDK/WDK all of them are connected from static library, instead of imported from DLL. And in what sense to do for them separate dll? These functions if I am not mistaken, are implemented in heading files and the compiler can is quite good  the code with their involvement...

3

Re: Whether is generally available DLL with strsafe-functions?

Hello, Evgenie Muzychenko, you wrote: I eat> MS and did not find time to suppose them in generally available DLL how lstrXxx and w [v] sprintf, or I that do not understand? Well, for themselves they supposed functions like wcscat_s in ntdll

4

Re: Whether is generally available DLL with strsafe-functions?

Hello, okman, you wrote: O> are implemented in heading files and the compiler can is quite good  the code with their involvement... With such approach it is possible an unlimited part standard DLL in titles to drag. Would make on a choice - the same memcpy/memset and other from time immemorial is in intrinsic. Me, actually, there first of all printf-functions always interested. In a kernel always it is possible  to export from ntoskrnl, and in the user process - only to wsprintf from user32 or wnsprintf from shlwapi. The first does not have restriction on the size of the buffer, and at both formatting possibilities are cut off. About the first till now frighten in the documentation that end of a line in zero though I since XP in one implementation did not meet not complete lines is not guaranteed. And dynamic  with CRT is or to put necessary DLL in the distribution kit, or regularly to face absence necessary DLL in system.

5

Re: Whether is generally available DLL with strsafe-functions?

Hello, Evgenie Muzychenko, you wrote: I eat> With such approach it is possible an unlimited part standard DLL in titles to drag. By the way, quite good idea)) I eat> Me, actually, there first of all printf-functions always interested. In a kernel always it is possible  to export from ntoskrnl, and in the user process - only to wsprintf from user32 or wnsprintf from shlwapi. The first does not have restriction on the size of the buffer, and at both formatting possibilities are cut off. About the first till now frighten in the documentation that end of a line in zero though I since XP in one implementation did not meet not complete lines is not guaranteed. I eat> And dynamic  with CRT is or to put necessary DLL in the distribution kit, or regularly to face absence necessary DLL in system. So and in what was specific a problem with StringCchPrintf, for example? I cause StringCchPrintf, the compiler/komponovshchik packs it in exe, outside does not stick out any  to another dll. At the same time there are no links unnecessary (sometimes) on user32/shlwapi32 which in certain cases only hinder. All are happy, all laugh. Unless not so?.

6

Re: Whether is generally available DLL with strsafe-functions?

Hello, okman, you wrote: O> I cause StringCchPrintf, the compiler/komponovshchik packs it in exe, outside does not stick out any  to another dll. Type, it is necessary to declare idea of the divided code of the inconsistent? O> at the same time there are no links unnecessary (sometimes) on user32/shlwapi32 which in certain cases only hinder. In what cases they can hinder, except links on rather new DLL which are not present in old systems? If there is a task to make EXE which will work and in Win95 - other question, but now even XP does not meet almost, not to mention earlier systems. I ceased to support several years ago 2k, and still nobody complained.