From: "Christopher Nelson" To: Subject: Re: DJGPP: the future is... ? Date: Sat, 27 Mar 1999 12:39:43 -0700 Message-ID: <01be7889$904d72c0$LocalHost@thendren> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Reply-To: djgpp AT delorie DOT com Dream List: (although I'm currently using 2.01, these might have been fixed in newer version.) libc: Threads, Sockets, REAL DLL's. debugger: REAL Template Debugging, Tracing into inlines and header files. compiler: REAL template management (versus the -fno-implicit/-fno-external method) other: a Standardized GUI for DJGPP programs (not mandatory, obviously, but optional, and easily extendible.) a Graphical RHIDE! a Multithreaded GCC! I know that some of these are dreams that will probably never be realized, but I honestly think that two of the most important things that we ought to do with DJGPP is, first of all, make it's libc thread-safe. This is the one huge benefit Linux and Windows have over DJGPP. (Well, maybe not Linux, since I really don't know much about Linux's kernel model, but typically UNIX's are built to be very parallel-able.) The second is the GUI. Hardly anyone does much work in console programs of any kind. The WEB is almost entirely graphical, almost all really cool games are entirely graphical, any sort of successful program today is graphical. Text-mode programs are often dismissed and ignored. And with good reason. Computers are plenty fast to support it, and it's simply a more intuitive, more flexible, more perfect method of interfacing with a program. If I had any sort of vote, I'd say Threads and a standardized GUI are two very important things almost entirely lacking in DJGPP. -={C}=-