Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!psuvax1!gatech!gitpyr!kyler
From: kyler@pyr.gatech.EDU (J. Kyle Rogers)
Newsgroups: comp.windows.ms
Subject: Re: Generic in Large Model
Keywords: STATE OF GEORGIA  DO NOT DUPLICATE
Message-ID: <9404@pyr.gatech.EDU>
Date: 21 Oct 89 05:50:21 GMT
References: <7887@microsoft.UUCP> <246@spot.wbst128.xerox.com> <82@venice.SEDD.TRW.COM>
Reply-To: kyler@pyr.UUCP (J. Kyle Rogers)
Organization: Georgia Institute of Technology
Lines: 32

In article <82@venice.SEDD.TRW.COM> press@venice.sedd.trw.com (Barry Press) writes:
>In article <246@spot.wbst128.xerox.com> Tomer.wbst@Xerox.COM (Shmuel Tomer) writes:
>>[...] is there any way you could call C library functions (eg,
>>strcmp, sprintf), using data from that additional memory? Do you have to
>>re-implement any such function? [...]

>You can do string and some other things using some undocumented functions
>in the Windows kernel.

Is it true that these functions are no longer present in Windows 3.0?

>You can feed mixed arguments to sprintf using the modifiers
>that specify near and far addressing -- see the printf documentation.

>Barry Press

I seem to remember a difference between the specification strings for
sprintf in the MSC 5.1 standard library and the sprintf in the Windows
library.  I may be wrong about that, but in medium model I routinely
use a call like the following, which works fine.

        sprintf (szBuffer, "Local String = %s  Global String = %Fs",
                 szLocalString, lpszGlobalString);

Here, the 'F' is a modifier telling sprintf to expect a FAR pointer;
I believe there is also a modifier 'N' to tell sprintf to expect a
NEAR pointer, but that is the default anyway in medium model.

|              krogers  --  J. Kyle Rogers  --  P.O. Box 31467               |
|           Georgia Insitute of Technology, Atlanta Georgia, 30332           |
|uucp: ...!{akgua,allegra,amd,hplabs,ihnp4,seismo,ut-ngp}!gatech!gitpyr!kyler|
|ARPA: kyler@pyr.gatech.edu                                                  |