www.delorie.com/archives/browse.cgi | search |
From: | brennan AT mack DOT rt66 DOT com (Brennan "The Rev. Bas" Underwood) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Allegro future |
Date: | 14 Dec 1996 17:42:39 -0700 |
Organization: | Rasterfari |
Lines: | 18 |
Message-ID: | <58vhhv$dbk@mack.rt66.com> |
References: | <m0vXru4-000S1dC AT natacha DOT inti DOT edu DOT ar> |
NNTP-Posting-Host: | mack.rt66.com |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
In article <m0vXru4-000S1dC AT natacha DOT inti DOT edu DOT ar>, Salvador Eduardo Tropea (SET) <salvador AT natacha DOT inti DOT edu DOT ar> wrote: >> 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 Why leave out C programmers? Just create C++ wrappers for what you want to be OO. Trivial really. And fast with inline methods. --Brennan -- brennan AT rt66 DOT com | "Developing for Windows is not fun." -- John Carmack Riomhchlaraitheoir| Rasterfarian | <http://brennan.home.ml.org> -O
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |