home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.tcl
- Path: sparky!uunet!eco.twg.com!twg.com!news
- From: "David Herron" <david@twg.com>
- Subject: Re: Tcl 6.4 Tcl_ParseVar bug OR gcc 2.2.2 bug?
- Message-ID: <1992Dec31.234740.14998@twg.com>
- Sensitivity: Personal
- Encoding: 18 TEXT , 4 TEXT
- Sender: news@twg.com (USENET News System)
- Conversion: Prohibited
- Organization: The Wollongong Group, Inc., Palo Alto, CA
- Conversion-With-Loss: Prohibited
- Date: Thu, 31 Dec 1992 23:47:01 GMT
- Lines: 23
-
- > |> In my opinion, Tcl should reallocate new space for its input and
- > |> manipulate that. With the use of gcc (and other ANSI conformant)
- > |> compilers becoming more widespread, ...
-
- ..
- > Ultimately I should fix Tcl, but this probably isn't going to happen
- > for version 7.0.
-
- Okay so since there's a bit of time to think about this problem ..
-
- Tcl shouldn't *always* realloc its input &c. Every time I've studied the
- performance of something, malloc() & friends turned out to be quite expensive
- and something to avoid when not necessary. This proposal to strdup() all the
- time may be big a problem.
-
- Some tricks might/could be pulled though since `most' command strings
- are short it'd be safe to allocate on the stack. (At least on virtual-memory
- systems anyway).
-
- <- David Herron <david@twg.com> (work) <david@davids.mmdf.com> (home)
- <-
- <- "Unix is a great idea being sold by companies who couldn't sell
- <- fast food in Somalia." - bill davidsen <davidsen@ariel.crd.GE.COM>
-