Path: utzoo!attcan!uunet!microsoft!kensy
From: kensy@microsoft.UUCP (Ken SYKES)
Newsgroups: comp.windows.ms
Subject: Re: Show-stopper in wstdio.c/3.0 SDK tty sample app
Keywords: Win 3.0 SDK, tty sample app, wstdio.c, LocalAlloc, LocalLock
Message-ID: <57647@microsoft.UUCP>
Date: 23 Sep 90 03:20:18 GMT
References: <6589@sugar.hackercorp.com>
Reply-To: kensy@microsoft.UUCP (Ken SYKES)
Organization: Microsoft Corp., Redmond WA
Lines: 16

In article <6589@sugar.hackercorp.com> karl@sugar.hackercorp.com (Karl Lehenbauer) writes:
>The wstdio.c module in the tty sample application has some code that
>By the way, with respect to all the people who are down on large model,
>how big are your applications, anyway?  64K of code space doesn't really
>go very far for any "real" application, I don't think.

Using small model doesn't limit you to 64K of code.  The way to get around
the 64K limit is to break the code into segments and prototype all of your
functions that will be called from another segment as FAR.  The -NT switch
will allow you to specify what segment each C module goes into.  It may
sound like a pain but the advantage is everything defaults to near code,
near data, unless you specify otherwise.  I have code that is a few 
hundred K that uses this technique.

Ken Sykes
Disclaimer: The above opinions are solely my own.