www.delorie.com/archives/browse.cgi | search |
From: | "r. v. paasen" <R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Allegro future |
Date: | Wed, 11 Dec 1996 00:58:58 +0100 |
Organization: | Eindhoven University of Technology, The Netherlands |
Lines: | 17 |
Message-ID: | <32ADF942.6A13@stud.tue.nl> |
References: | <32ACC368 DOT FA3 AT nlc DOT net DOT au> <58k7bo$rov AT news DOT csus DOT edu> |
Reply-To: | R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl |
NNTP-Posting-Host: | annex1s19.urc.tue.nl |
Mime-Version: | 1.0 |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Apparently-To: | djgpp AT delorie DOT com |
GEORGE ARUGAY MONTEMAYOR wrote: > > shaman AT nlc DOT net DOT au wrote: > : Another question: Why is allegro pure C? Why not C++? Some of the > : things in allegro are just crying out for proper OO. Take the bitmaps > : for example. Now we have "create_bitmap" and "destroy_bitmap". Why not > > One word: speed. OO is slow. > > -george Another word: disagree. Richard. ------------------------------------------- email: <mailto:R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl> www: <http://huizen.dds.nl/~buddha/>
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |