Path: utzoo!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!shlump.nac.dec.com!decuac!news
From: baker@wbc.enet.dec.com
Newsgroups: comp.sys.amiga.programmer
Subject: Size limits on  SAS/C object libraries...
Message-ID: <1991Mar18.181402.14674@decuac.dec.com>
Date: 18 Mar 91 18:06:06 GMT
Organization: Digital Equipment Corporation
Lines: 17

-Message-Text-Follows-

	Using OML to add modules to an object library, I
	discovered that it became unhappy when the resulting
	library exceeded 256K bytes.  As a workaround, I
	ended up breaking my library into two pieces, but
	in terms of the functionality of the library, this
	isn't very elegant.

	Questions: Is this just a limitation on OML's internal
	bookkeeping, or is there something in BLINK that wouldn't
	be able to handle huge object libraries ?  If it's not a
	BLINK issue, has anyone written an object librarian that
	can cope with big libraries ?

	Regards,
	 Art Baker