Message-ID: <3857030A.5E9D84F4@snetch.cpg.com.au> Date: Wed, 15 Dec 1999 13:55:06 +1100 From: Michael Abbott aka frEk <20014670 AT snetch DOT cpg DOT com DOT au> Organization: Student of Computer Power Institute X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: Questions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com Heya Wilmer van der Gaast wrote: > On Thu, 13 Jan 2000, Muntean George Andrei wrote: > > > other programming languages. I see that allegro is a library especially > > for making games. > > I would like to make games. I have some ideas. I saw that your program > > is perfect for me. > Why does everybody use libraries like Allegro??? Isn't it way more fun > to assemble your own library, so you don't have to work with a uncomfortable > API, but with an API that's exactly the way you like it??? Time... It takes less time to link in Allegro then to assemble the stuff yourself... Also Allegro has been fine tuned by a lot of people whereas you're just one person taking a shot at it :) If you're really serious about speed, etc. in that case you could use the allegro blit functions, etc. and then once the project is finished you could write your own functions tailored to specific needs... For example: A tile game which has a background layer of tiles that move around... blit() needs to clip in every possible situation but if you were writing it, you only need to clip when the tiles are slightly to almost completely on the screen (The tiles around the edges of the screen). Allegro is definitely fast enough for most of todays uses tho' but when you need more speed you need more speed :) > Oh yeah, I'm a geek... That must be the problem... Cool! That makes two of us :) - Michael