Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ns-mx!ccad.uiowa.edu!cadsi
From: cadsi@ccad.uiowa.edu (CADSI)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Gawd I love this shit.  Q about strings in windows
Message-ID: <1991Mar3.215408.21076@ccad.uiowa.edu>
Date: 3 Mar 91 21:54:08 GMT
References: <1991Mar3.194444.26873@javelin.es.com>
Organization: CAD-Research, U. of Iowa, Iowa City, Iowa
Lines: 19

From article <1991Mar3.194444.26873@javelin.es.com>, by lwallace@javelin.es.com (Lynn Wallace):
> I've found that many of the string functions~ don't work in Windows, 
> particularly strcpy.  I haven't been able to find any discussion of string
> manipulation in the dox, particularly the Guide to Programming.  Can anyone
> point me to a good discussion of it, or possibly point out some caveats?
> 
> Ya know, what I'm trying to write is really not that complicated.  But whenever
> I try something new (meaning something I simply haven't tried under Windows
> but have done many times in other environments) it takes several days to figure
> out some silly little extra thing I've got to do to make it work.  Assuming
> I'm successful at all and don't end up kludging a way around it.  This is the
> first and last application I will try to write using just the SDK.

	Welcome to the world of SDK!  The strxxx functions in general aren't
what you want.  If you use the SDK's lstrcpy and other such functions, things
will probably work out.  Windows in general wants to mess with far pointers.
depending on your memory model during compilations, strcpy will use far or
near pointers, exclusive or I mean.  This info is really in the dox as you put
it.