Date: Mon, 8 Mar 1999 22:58:31 -0500 Message-Id: <199903090358.WAA20971@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: djgpp AT delorie DOT com In-reply-to: <1M0F2.28020$Hn5.6688@newsfeeds.bigpond.com> (jventer AT writeme DOT com) Subject: Re: Is Allegro too slow for 648 * 480 double buffering ? References: <1M0F2.28020$Hn5 DOT 6688 AT newsfeeds DOT bigpond DOT com> Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Would the __dgpp_nearptr_enable/disable functions have been one of > the results of iD's 'footprint in the sand'? What other changes did > they ask for? That was the biggie. I think the rest were bug fixes and minor features, but I wasn't the one working directly with them. > BTW Why did they stop using DJGPP? Or was Quake 2 also written with it? If I recall correctly, they wanted to take advantage of 3D hardware (OpenGL), and at the time, DJGPP didn't support it, so they switched to a windows-based development system.