home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!rpi!uwm.edu!ogicse!reed!bowman
- From: bowman@reed.edu (Eric Bowman (bobo))
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: THINK C linker makes me sad
- Message-ID: <1992Sep8.085120.24380@reed.edu>
- Date: 8 Sep 92 08:51:20 GMT
- Article-I.D.: reed.1992Sep8.085120.24380
- References: <fdrny7c.howard@netcom.com>
- Distribution: usa
- Organization: Reed College, Portland, OR
- Lines: 29
-
- In article <fdrny7c.howard@netcom.com> howard@netcom.com (Howard Berkey) writes:
- >So I was writing this really small, simple app. (a mac version of xclock,
- >just for fun.) It was only 3k. Then I added a call to sprintf(). It
- >exploded the program to 22k.
-
- I hate to break it to you, but it ain't the linker's fault. printf is BIG.
- In MPW C you can get rid of some of it if you don't do any floating point
- conversions; I suspect you can do something similar with Think.
-
- Basically, using printf isn't such a great idea, IMO. Sure, it's easy to
- use, but I've found it better/smaller/faster in the long run to use
- NumToString, etc.
-
- >Please, no flames for this... I LOVE the THINK C environment, and I know
- >that the 'open letter to symmantec' thread was months ago, but I do REALLY
- >WISH that the THINK C linker (or loader) would recognize discrete blocks of
- >code at the function (rather than file) level.
-
- Isn't Think 5 better about this?
-
- > While I'm at it some revision control system would be nice too...
-
- Gotta love Projector! :-)
-
- later,
- bobo
- bowman@reed.edu
- George Clinton in '92
- Congress No! Parliament Yes!
-