🚀 go-pugleaf

In <1993Jan23.042005.15653@netcom.com> yikes@netcom.com (Michael Brill) writes:

<Porting from the NeXT to Windows or the Mac>

>As far as the UI goes, I'm not going to worry about now.  What I
>am worried about is memory management.  I've scanned through the
>Windows docs and understand how memory management works there
>(getting handle, locking, operating, unlocking) and I'm looking
>for an established scheme to make the port seamless between Unix
>and Windows/Mac.

There a few things you should consider regarding Window's memory management:

1.	Target Standard and Enhanced mode.  Windows 3.0 Real mode is dead.
2.	Static data and the stack are confined to the same 64k segment (If you
	wish to run multiple instances of your app)
3.	The use of 64k+ data objects is a bit troublesome.
4.	Global memory handles are limited, use subsegment allocation.  
	Subsegment allocation is supported by Borland's and Microsoft's 
	compilers, a source can also be obtained in Paul Yao's 'Power 
	Programming For Windows'.

Buy a good Windows memory management book:
	'DLL's and Memory Management'


>Does targeting Win32 make life any easier for me?

Easier porting yes, easier marketing no (not today at least).

>Thanks, ...Michael Brill (yikes@netcom.com)

Karl
-- 

\ Internet: karlth@rhi.hi.is             \ Karl Thoroddsen University Of Iceland
 \ Respect...            , Peter Ustinov  \ Department Of Computer Science