Date: Thu, 29 Aug 1996 17:34:51 +0200 (MET DST) From: Mark Habersack Reply-To: grendel AT ananke DOT amu DOT edu DOT pl To: Elliott Oti cc: djgpp AT delorie DOT com Subject: Re: DJGPP and Mirosoft Foundation Classes In-Reply-To: <321A03DB.7E13@stud.warande.ruu.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 20 Aug 1996, Elliott Oti wrote: >> the collection classes, the CString class and the CFile class. Do anybody know >> about libraries which i can use to compile my programm with gcc without >> writing it completely new >> >> tanhk you for any information >> >> Michael Plagge >> plaggmi AT uni-muenster DOT de > >That's a good one. I don't believe there are ANY ports of MFC (or OWL, for that >matter) to DJGPP. There is an ongoing port of the standard templates library, >but porting MFC would be no minor project IMHO. I think porting MFC to DJGPP (and for that matter to any gcc environment) is pointless. MFC is a great example of bad OOP programming. It looks like old C code wrapped up with C++ classes. In addition MFC is one of the biggest (I mean in terms of occupied disk space - VC4 has ~180 of it on the CD!!!! That's ridiculous!) and the slowest frameworks ever created. I used to think OWL is slow, but when I saw the MFC at work... If one wanted to port such a library to gcc, s/he should choose OWL. Why? Well, OWL is an excellent example of C++ OOP - although also quite slow. Besides the great advantage of OWL is that it is already ported to OS2. It is available in Borland compilers for this OS. OWL, however, uses many of Borland-specific C++ extensions and exception handling which is not supported in gcc (well, it is but there's much left to do). Anyway, my opinion is that porting MFC is just a waste of time. >Might be a good idea to email Microsoft ( and Borland) and worry them to make a >DJGPP port of MFL and OWL, or at least assist. DJGPP is growing in popularity and use, >but the big software corporations still refuse to acknowledge it as a market >(OK, maybe it isn't a market :) I don't suppose that such profit-bound companies would be interested in active support of porting their products to free-ware compilers/systems. >Right now DJGPP isn't a Windows oriented compiler, and general supporting With relatively small effort you can create Win32 apps. There are only two features missing in this support: DLLs and Win32s apps (but who really needs them today? I mean the Win32s apps.). AFAIK, the problem with DLLs is that DJGPP doesn't produce appropriate relocations for shared libraries (or was ot ld? ;-)))) Mark /************************************************************/ /** Maybe it was infatuation or the thrill of a chase? **/ /** Maybe you were always beyond my reach and my heart **/ /** was playing safe? ***********/ /** But was that love in your eyes I saw, **/ /** or the reflection of mine? **/ /** I'll never really know for sure, **/ /** You never really gave me time! **/ /** Won't you give me that time? **/ /** "Cindirella Search" **/ /********************************/ Visit my homepage: http://ananke.amu.edu.pl/~grendel