Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!oliveb!apple!vsi1!wyse!mips!prls!philabs!ttidca!hollombe From: hollombe@ttidca.TTI.COM (The Polymath) Newsgroups: comp.sys.ibm.pc Subject: Re: Turbo C vs. Pascal Message-ID: <4006@ttidca.TTI.COM> Date: 8 Mar 89 01:06:18 GMT References: <46500039@uxf.cso.uiuc.edu> Reply-To: hollombe@ttidcb.tti.com (The Polymath) Organization: The Cat Factory Lines: 34 In article <46500039@uxf.cso.uiuc.edu> mwh1629@uxf.cso.uiuc.edu writes: }... C seems }to compile huge. A program to print "Hello, world." on the screen }compiled to 9k, while a program to print out a table of numbers and sort }them in Turbo Pascal only took 6k. ... Have you tried turning off all the debug hooks and bounds checking Turbo-C puts in by default? That will usually shrink a program considerably. Also, the printf() family in C includes some very powerful formatting capabilities that require significant code to implement. A simple putch() loop is all you need for "Hello world.". } I also have two general questions. If you compile a program with a language }and then commercially release it are you required to pay some money to the }compiler's maker? Depends on the licensing agreement. Borland is quite reasonable about this. Their only requirement is that your code include a copyright declaration. Yours or theirs, it doesn't matter, but your code must be copyrighted. }Lastly, what's the deal with version numbers? I think I }was told that, for example, Version 2.34 means that 4 is a bug fix, 3 is a }minor improvement and 2 is a major change. Is this correct? This probably varies by manufacturer. Major vs. minor vs. bug fix are rather subjective, anyway. Ask and they might tell you, but don't expect anyone to call a bug fix a bug fix. (-: -- The Polymath (aka: Jerry Hollombe, hollombe@ttidca.tti.com) Illegitimati Nil Citicorp(+)TTI Carborundum 3100 Ocean Park Blvd. (213) 452-9191, x2483 Santa Monica, CA 90405 {csun|philabs|psivax}!ttidca!hollombe