Path: utzoo!utgpu!water!watmath!clyde!rutgers!princeton!udel!gatech!ukma!psuvm.bitnet!cunyvm!ndsuvm1.bitnet!ud046803 From: UD046803@NDSUVM1.BITNET Newsgroups: comp.sys.ibm.pc Subject: Turbo Pascal to Microsoft QuickC Translator Message-ID: <544UD046803@NDSUVM1> Date: 21 Jan 88 22:14:41 GMT Organization: North Dakota Higher Education Computer Network, Fargo, ND Lines: 32 DISCLAIMER: Author bears full responsibility for contents of this article. Well, I just received the Turbo Pascal to QuickC Translator and very anxious to try it out. So I write a trivial Pascal program and it translates without any problem. And then I compile with my Microsoft C compiler. And it RUN with no problem. Wow what A GOOD PRODUCT!! But WAIT! WHAT?? The EXE file that the C compiler generate is a whopping 95K in size compare to 11K for the good old Turbo Pascal COM file. And that is not what I want for a translator. I want to write in C because I want faster execution and more compact code, not something like this. It turns out it didn't really translate to microsoft C, instead it translate to a whole bunch of turbo pascal call. And then you link you basic C program to the turbo Pascal-C library. Also due to compatibility problem between C and Turbo Pascal (4 byte data and code pointer), you need to compile the resulted C prorgam using large Model. And why would I want to compile a small model Pascal program into large model C program without having any benefit. What I want(?) is a translator which translate to pure microsoft C code or any C code use their own C library, not another set of library. May be I should rewrite to C by myself instead of using the translator. Being a good C programmer myself, I think that is the logical thing to do. The translator should ease the pain of novice programmer who want to translate Pascal to C. Don't take me wrong, I think Microsoft are releasing the translator in good faith, but it just didn't work out for the majority of C programmer. Is anybody have something to say about the translator? ------------------------------------------------------------------------------- Should we wait for the 80986 or shouldn't we??? Or should we go for the 68090? Larry Siu ....... UD046803@NDSUVM1